Mmcp.market

product-strategy skill

by phuryn·phuryn/pm-skills·27k stars·MIT

Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. Use when building a product strategy, creating a strategic plan, or defining product direction.

A100/100content scan

Is the product-strategy skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the product-strategy skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-product-strategy/skills/product-strategy ~/.claude/skills/product-strategy
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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

  1. Define the vision and aspirational impact
  2. Identify 2-3 target market segments with their JTBD
  3. Establish cost positioning (low cost vs. premium value)
  4. Develop value propositions for each segment
  5. List explicit trade-offs (what we won't do)
  6. Set North Star and quarterly OMTM
  7. Outline growth strategy and channels
  8. Document required capabilities and partnerships
  9. Explain defensibility and barriers to competition
  10. Validate strategy coherence: ensure elements reinforce each other
  11. Surface critical hypotheses that must be true for success
  12. 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

  • Product Strategy Canvas (PPTX)

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)

More skills from phuryn/pm-skills

  • Aab-test-analysisAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
  • Aanalyze-feature-requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
  • Aansoff-matrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
  • Abeachhead-segmentIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
  • Abrainstorm-experiments-existingDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
  • Abrainstorm-experiments-newDesign lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
  • Abrainstorm-ideas-existingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
  • Abrainstorm-ideas-newBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
  • Abrainstorm-okrsBrainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
  • Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
  • Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
  • Acohort-analysisPerform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.

All agent skills → · MCP servers