brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Run a positioning workshop that surfaces target customer, unmet need, category, benefits, and differentiation. Use when your product messaging feels fuzzy, generic, or misaligned.
$ npx -y skills add getcrew44/crew44 --skill positioning-workshop --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/positioning-workshopContext 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.
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"
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.
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`)
---
Use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the default interaction protocol for this skill.
It defines:
This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
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.
---
**Agent suggests:**
Before we begin, let's gather product context to ground our positioning work:
**For Your Own Product:**
**For Repositioning an Existing Product:**
**If You Don't Have a Product Yet (or Want to Benchmark):**
**You can paste this content directly, or we can proceed with a brief description.**
---
**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
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.
Repo: getcrew44/crew44
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes