Structured workshop to discover and articulate product positioning through guided questions about target customers, unmet needs, category, benefits, and differentiation.
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
Fetches positioning-workshop from deanpeters/product-manager-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/positioning-workshop
Restart Cursor to activate positioning-workshop. Access via /positioning-workshop in your agent's command palette.
⚠
Security Notice
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.
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.
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):
Business management software — E.g., "All-in-one platform for operations (invoicing, payroll, CRM)" (like HubSpot, Zoho)
Vertical SaaS — E.g., "Purpose-built for a specific industry (e.g., HVAC, legal, dental)" (like Jobber, Clio)
AI-powered assistant — E.g., "AI tool that automates workflows via natural language" (like Notion AI, Jasper)
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]
Question 4: Key Benefit (Outcome, Not Features)
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):
Time savings — E.g., "Reduces manual work from 10 hours/week to 1 hour" (measurable efficiency)
Error reduction — E.g., "Eliminates 95% of manual data entry errors" (accuracy/risk mitigation)
Cost savings — E.g., "Saves $500/month in labor costs by automating invoicing" (direct ROI)
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]
Question 5: Competitive Differentiation
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):
Incumbent SaaS leader — E.g., "Unlike Zapier (which requires technical setup), we offer no-code visual workflows accessible to non-technical users"
Spreadsheets/manual processes — E.g., "Unlike Excel (which requires manual updates), we provide real-time automated sync across tools"
Vertical competitor — E.g., "Unlike generic automation tools, we're pre-built for [industry] with templates and compliance features"
Enterprise-only solutions — E.g., "Unlike enterprise tools (complex, expensive), we're designed for SMBs with simple pricing and 10-minute setup"
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]
Output: Generate Positioning Statement
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 Steps1.**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?**
Examples
Example 1: Good Positioning Workshop (B2B SaaS Automation)
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"
## 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 SummaryAcme 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:
Target is specific (SMB owners, 10-50 employees, operations focus)
Need is measurable (10+ hours/week on manual tasks)
Category is clear (workflow automation)
Benefit is outcome-focused (10 hours → 1 hour)
Differentiation is defensible (no-code vs. technical setup)
›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
