Skip to content
Development
Skill

/positioning-workshop

Run a positioning workshop that surfaces target customer, unmet need, category, benefits, and differentiation. Use when your product messaging feels fuzzy, generic, or misaligned.

From plugin
crew44
35862 skills4 agents
Install
$ npx -y skills add getcrew44/crew44 --skill positioning-workshop --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/positioning-workshop

Context preview

The summary Claude sees to decide when to auto-load this skill.

Run a positioning workshop that surfaces target customer, unmet need, category, benefits, and differentiation. Use when your product messaging feels fuzzy, generic, or misaligned.

SKILL.md

positioning-workshop.SKILL.md
name: positioning-workshop
description: Run a positioning workshop that surfaces target customer, unmet need, category, benefits, and differentiation. Use when your product messaging feels fuzzy, generic, or misaligned.
intent: >-
  Guide product managers through discovering and articulating product positioning by asking adaptive questions about target customers, unmet needs, product category, benefits, and competitive differentiation. Use this to align stakeholders on strategic positioning before writing PRDs, launch plans, or marketing materials—ensuring you've made deliberate choices about who you serve, what need you address, and how you differ from alternatives.
type: interactive
best_for:
  - "Running a workshop to sharpen product positioning"
  - "Clarifying target customer, category, and differentiation"
  - "Fixing fuzzy or generic messaging before launch"
scenarios:
  - "Help me run a positioning workshop for our B2B analytics product"
  - "Our messaging feels generic. Facilitate a positioning session."
  - "We need to define who we serve and why we're different"

Purpose

Guide product managers through discovering and articulating product positioning by asking adaptive questions about target customers, unmet needs, product category, benefits, and competitive differentiation. Use this to align stakeholders on strategic positioning before writing PRDs, launch plans, or marketing materials—ensuring you've made deliberate choices about who you serve, what need you address, and how you differ from alternatives.

This is not a brainstorming session—it's a structured discovery process that outputs a Geoffrey Moore positioning statement backed by evidence and strategic choices.

Key Concepts

The Positioning Workshop Flow

An interactive discovery process that: 1. Gathers product context (marketing materials, competitor intel) 2. Identifies target customer segment through questioning 3. Uncovers underserved needs via Jobs-to-be-Done lens 4. Defines product category and benefits 5. Establishes competitive differentiation 6. Outputs a complete positioning statement (uses `positioning-statement.md`)

Why This Works

  • **Structured discovery:** Prevents "positioning by committee" (too vague)
  • **Evidence-based:** Uses real marketing materials, customer feedback, competitive intel
  • **Adaptive:** Questions adjust based on B2B vs. B2C, new product vs. repositioning, etc.
  • **Actionable output:** Generates a Geoffrey Moore positioning statement ready for stakeholder review

Anti-Patterns (What This Is NOT)

  • **Not a tagline generator:** Positioning ≠ marketing copy
  • **Not feature-first:** Starts with customer problems, not product capabilities
  • **Not consensus-driven:** Forces hard choices (can't be "for everyone")

When to Use This

  • Defining positioning for a new product
  • Repositioning an existing product (pivot, market shift)
  • Aligning stakeholders on product strategy
  • Preparing for launch or major release
  • Before writing positioning-dependent artifacts (PRD, press release, sales deck)

When NOT to Use This

  • Before customer research (positioning requires validated insights)
  • For internal tools with captive users (no market positioning needed)
  • When positioning is already clear and validated

---

Facilitation Source of Truth

Use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the default interaction protocol for this skill.

It defines:

  • session heads-up + entry mode (Guided, Context dump, Best guess)
  • one-question turns with plain-language prompts
  • progress labels (for example, Context Qx/8 and Scoring Qx/5)
  • interruption handling and pause/resume behavior
  • numbered recommendations at decision points
  • quick-select numbered response options for regular questions (include `Other (specify)` when useful)

This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.

Application

This interactive skill asks **up to 5 adaptive questions**, offering **3-4 enumerated context-aware options** at each step.

Interaction pattern: Pair with `skills/workshop-facilitation/SKILL.md` when you want a one-step-at-a-time flow with numbered recommendations at decision points and quick-select options for regular questions. If the user asks for a single-shot output, skip the multi-turn facilitation.

---

Step 0: Gather Context (Before Questions)

**Agent suggests:**

Before we begin, let's gather product context to ground our positioning work:

**For Your Own Product:**

  • Current website copy (homepage, product pages, value prop)
  • Existing positioning statements or messaging docs
  • Customer testimonials or case studies
  • Sales objections or competitive win/loss analysis
  • Product descriptions or feature lists

**For Repositioning an Existing Product:**

  • Current positioning (what are you saying today?)
  • Customer feedback or support tickets (what problems do they report?)
  • Competitive intel (how do competitors position themselves?)

**If You Don't Have a Product Yet (or Want to Benchmark):**

  • Find 2-3 competitor or analog products
  • Copy their website homepage, positioning statements, or value props
  • We'll use these as reference points

**You can paste this content directly, or we can proceed with a brief description.**

---

Question 1: Target Customer Segment

**Agent asks:** "Based on the context provided, who is the primary customer segment you're serving?"

**Offer 4 enumerated options (adapted based on product context):**

1. **B2B: SMB decision-makers** — E.g., "Small business owners (10-50 employees) managing operations" (like Gusto, QuickBooks) 2. **B2B: Enterprise buyers** — E.g., "IT/Product leaders at companies with 500+ employees" (like Salesforce, Workday) 3. **B2C: Mass market consumers** — E.g., "Gen Z users (18-25) seeking budgeting tools" (like Mint, Venmo) 4. **B2C: Niche enthusiasts** — E.g., "Fitness enthusiasts tracking macros and workouts" (like MyFitn

Read more
Ships withcrew44

Orchestrate a crew of specialist AI agents in one local-first workspace. Each role on its best model, with memory and skills that compound. Free, MIT.

Get the whole plugin