Structured workshop to discover and articulate product positioning through guided questions about target customers, unmet needs, category, benefits, and differentiation.
Works with
Runs an interactive 5-question discovery process that outputs a Geoffrey Moore positioning statement backed by strategic choices, not guesses
Adapts questions based on product context (B2B vs. B2C, new product vs. repositioning) and gathers evidence from marketing materials, customer feedback, and competitive intel befo
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpositioning-workshopExecute the skills CLI command in your project's root directory to begin installation:
Fetches positioning-workshop from deanpeters/product-manager-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate positioning-workshop. Access via /positioning-workshop in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
3.1K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3.1K
stars
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:
positioning-statement.md)Use workshop-facilitation as the default interaction protocol for this skill.
It defines:
Other (specify) when useful)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):
Or describe your own target customer segment (be specific: demographics, role, company size, behaviors).
Adaptation tip: If marketing materials mention "enterprises," "SMBs," "consumers," or specific personas, suggest those.
User response: [Selection or custom]
Agent asks: "What underserved need or pain point does your target customer experience that your product addresses?"
Offer 4 enumerated options (adapted based on Question 1):
Example (if Q1 = B2B SMB decision-makers):
Or describe the specific pain point/unmet need based on customer research, support tickets, or competitive gaps.
Adaptation tip: Use language from customer testimonials or case studies in the provided materials.
User response: [Selection or custom]
Agent asks: "What product category does your solution fit into? (This anchors how buyers evaluate you.)"
Offer 4 enumerated options (adapted based on Q1 + Q2):
Example (if Q1 = B2B SMB, Q2 = Time-consuming manual work):
Or define your own category. Note: Creating a new category is risky—pick an existing one unless you have strong rationale.
Adaptation tip: If competitors are in a clear category, default to that unless you're deliberately creating a new one.
User response: [Selection or custom]
Agent asks: "What's the primary benefit or outcome your product delivers? (Focus on what the customer gets, not what the product has.)"
Offer 3 enumerated options (adapted based on Q2 need):
Example (if Q2 = Time-consuming manual work):
Or describe the specific, measurable outcome your product delivers.
Quality check: Avoid features ("has AI," "includes dashboards"). Focus on outcomes ("makes decisions 3x faster," "prevents compliance violations").
User response: [Selection or custom]
Agent asks: "What's your primary competitor or competitive alternative, and how do you differ?"
Offer 4 enumerated options (adapted based on Q3 category):
Example (if Q3 = Workflow automation platform):
Or describe your primary competitive alternative and your unique differentiation (focus on outcomes, not features).
Adaptation tip: Use competitive intel from provided materials (win/loss analysis, sales objections).
User response: [Selection or custom]
After collecting responses, the agent generates a positioning statement using the positioning-statement.md format:
# Positioning Statement
**Based on your responses, here's your positioning statement:**
---
## Value Proposition
**For** [Target customer from Q1]
- **that need** [Underserved need from Q2]
- [Product name]
- **is a** [Product category from Q3]
- **that** [Key benefit from Q4]
---
## Differentiation Statement
- **Unlike** [Primary competitor from Q5]
- [Product name]
- **provides** [Unique differentiation from Q5]
---
## Positioning Summary (One-Sentence Version)
[Product name] is a [category] for [target] that [benefit], unlike [competitor] which [limitation].
**Example:** "Acme Workflows is a no-code automation platform for small business owners that reduces manual work from 10 hours/week to 1 hour, unlike Zapier which requires technical setup and coding knowledge."
---
## Next Steps
1. **Stress-test this positioning:**
- Read it aloud to 5 target customers. Do they recognize themselves?
- Share with stakeholders (product, marketing, sales). Does it align?
- Check if differentiation is defensible (can competitors copy this in 6 months?).
2. **Refine based on feedback:**
- If target feels too broad → Narrow further (e.g., "SMB owners" → "SMB owners in service industries")
- If need isn't resonating → Validate with more customer research
- If category confuses → Pick a clearer category or commit to category creation
3. **Apply to artifacts:**
- Update website homepage and product pages
- Revise sales deck and pitch materials
- Use in PRD, press release, or roadmap planning (reference `press-release.md`, `positioning-statement.md`)
---
**Would you like to refine any part of this positioning, or shall we document it as final?**
Step 0 - Context Provided: User shares current website copy:
"Acme Workflows helps small businesses automate repetitive tasks. Connect your apps and save time."
Question 1 Response: "B2B: SMB decision-makers — Small business owners (10-50 employees) managing operations"
Question 2 Response: "Time-consuming manual work — Spend 10+ hours/week on invoice processing, data entry, reporting"
Question 3 Response: "Workflow automation platform — Automates repetitive tasks across apps"
Question 4 Response: "Time savings — Reduces manual work from 10 hours/week to 1 hour"
Question 5 Response: "Incumbent SaaS leader — Unlike Zapier (which requires technical setup), we offer no-code visual workflows accessible to non-technical users"
Generated Positioning Statement:
## Value Proposition
**For** small business owners (10-50 employees) managing daily operations
- **that need** to eliminate 10+ hours/week spent on manual tasks like invoice processing, data entry, and reporting
- Acme Workflows
- **is a** no-code workflow automation platform
- **that** reduces manual work from 10 hours/week to 1 hour by automating repetitive tasks across apps
## Differentiation Statement
- **Unlike** Zapier, which requires technical setup and coding knowledge
- Acme Workflows
- **provides** visual, no-code workflows that non-technical business owners can set up in 10 minutes
## Positioning Summary
Acme Workflows is a no-code automation platform for small business owners that reduces manual work from 10 hours/week to 1 hour, unlike Zapier which requires technical setup and coding knowledge.
Why this works:
Question 1 Response: "Businesses" Question 2 Response: "Need better tools" Question 3 Response: "Software" Question 4 Response: "Productivity" Question 5 Response: "We're better than competitors"
Generated Positioning Statement:
**For** businesses
- **that need** better tools
- ProductX
- **is a** software
- **that** improves productivity
✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
646mattpocock/skills
Productivitysame categorypremortem
213parcadei/continuous-claude-v3
Productivitysame categorydeslop
159cursor/plugins
Productivitysame categorytravel-planner
136ailabs-393/ai-labs-claude-skills
Productivitysame categoryframer-motion
131pproenca/dot-skills
Productivitysame categorywrite-a-prd
128mattpocock/skills
Productivitysame categoryReviews
4.7★★★★★60 reviews- SSakura Brown★★★★★Dec 20, 2024
Registry listing for positioning-workshop matched our evaluation — installs cleanly and behaves as described in the markdown.
- AArjun Bhatia★★★★★Dec 12, 2024
positioning-workshop reduced setup friction for our internal harness; good balance of opinion and flexibility.
- NNia Zhang★★★★★Dec 4, 2024
Keeps context tight: positioning-workshop is the kind of skill you can hand to a new teammate without a long onboarding doc.
- NNaina Abebe★★★★★Nov 23, 2024
Registry listing for positioning-workshop matched our evaluation — installs cleanly and behaves as described in the markdown.
- HHiroshi Okafor★★★★★Nov 11, 2024
Keeps context tight: positioning-workshop is the kind of skill you can hand to a new teammate without a long onboarding doc.
- NNeel Mehta★★★★★Nov 3, 2024
positioning-workshop is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- NNaina Torres★★★★★Oct 22, 2024
Keeps context tight: positioning-workshop is the kind of skill you can hand to a new teammate without a long onboarding doc.
- AAma Rahman★★★★★Oct 14, 2024
positioning-workshop reduced setup friction for our internal harness; good balance of opinion and flexibility.
- SSakura Patel★★★★★Oct 2, 2024
positioning-workshop is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- AAma Nasser★★★★★Sep 25, 2024
Useful defaults in positioning-workshop — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 60
1 / 6Discussion
Comments — not star reviews- No comments yet — start the thread.