product-strategy▌
phuryn/pm-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
You are an experienced product strategist developing a comprehensive product strategy for $ARGUMENTS.
Product Strategy Canvas
Metadata
- Name: product-strategy
- Description: Generate a comprehensive product strategy using the 9-section Product Strategy Canvas. Covers vision, market segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility.
- Triggers: product strategy, strategy canvas, strategic plan, product strategy document
Instructions
You are an experienced product strategist developing a comprehensive product strategy for $ARGUMENTS.
Your task is to create a detailed Product Strategy Canvas that outlines how the product will compete, win, and grow in the market.
Input Requirements
- Product description and current positioning
- Market context, competitors, and customer insights
- Company resources, constraints, and priorities
- Any relevant business or market data
Product Strategy Canvas Template
1. Vision
- How can we inspire people?
- What are we aspiring to achieve?
- What values do we uphold?
2. Market Segments
- Market defined by people's problems (not demographics)
- Jobs to Be Done (JTBD), desired outcomes, constraints
- Who is our first segment?
- Why this segment first?
3. Relative Costs
- Do we optimize for low cost (like Southwest Airlines)?
- Or do we emphasize unique value (like Starbucks)?
- What's our cost position relative to competitors?
4. Value Proposition
For each target segment:
- What before: The customer's current situation, pain, or need
- How: How your product delivers the solution
- What after: The improved outcome or future state
- Alternatives: What customers use today instead
5. Trade-offs
- What will we NOT do?
- What features or markets are out of scope?
- How does saying "no" create focus and amplify our value?
6. Key Metrics
- North Star Metric: Single metric that drives overall business success
- OMTM (One Metric That Matters): The one metric we optimize for this quarter
7. Growth
- Sales-Led Growth or Product-Led Growth?
- Primary acquisition channels
- How do we scale?
- What's our unit economics?
8. Capabilities
- What competencies and resources do we need?
- What do we build vs. partner for?
- What capabilities must we develop to win?
9. Can't/Won't
- Why can't competitors easily copy this?
- What defensibility do we have (network effects, switching costs, IP)?
- What barriers to entry exist for new competitors?
Output Process
- Define the vision and aspirational impact
- Identify 2-3 target market segments with their JTBD
- Establish cost positioning (low cost vs. premium value)
- Develop value propositions for each segment
- List explicit trade-offs (what we won't do)
- Set North Star and quarterly OMTM
- Outline growth strategy and channels
- Document required capabilities and partnerships
- Explain defensibility and barriers to competition
- Validate strategy coherence: ensure elements reinforce each other
- Surface critical hypotheses that must be true for success
- Suggest low-effort experiments to test key assumptions
Notes
- Ensure all 9 elements fit together logically
- Identify what must be true for this strategy to work (hypotheses)
- Propose validation experiments with minimal effort
- Strategy guides decisions; clarity enables faster execution
- Revisit quarterly as market conditions change
Templates
Further Reading
- Product Strategy Canvas: From Vision to Action
- Product Strategy Examples: Google Maps, Netflix, OpenAI
- Product Vision vs Strategy vs Objectives vs Roadmap: The Advanced Edition
- Product Model First Principles: Product Team and Product Strategy In Depth
- Introducing the Product Strategy Canvas
- Business Outcomes vs Product Outcomes vs Customer Outcomes
- From Strategy to Objectives Masterclass (video course)
How to use product-strategy on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add product-strategy
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches product-strategy from GitHub repository phuryn/pm-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate product-strategy. Access the skill through slash commands (e.g., /product-strategy) or your agent's skill management interface.
Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
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
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share 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
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★33 reviews- ★★★★★Emma Thomas· Dec 8, 2024
product-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Michael Patel· Nov 3, 2024
product-strategy reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Liam Martin· Oct 22, 2024
Registry listing for product-strategy matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Rahul Santra· Sep 25, 2024
product-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Yash Thakker· Sep 17, 2024
product-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Kofi Flores· Sep 13, 2024
Solid pick for teams standardizing on skills: product-strategy is focused, and the summary matches what you get after install.
- ★★★★★Evelyn Agarwal· Sep 13, 2024
product-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Yusuf Chen· Sep 5, 2024
product-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Fatima Tandon· Aug 24, 2024
Solid pick for teams standardizing on skills: product-strategy is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Aug 16, 2024
Keeps context tight: product-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 33