strategy · phuryn — Claude Code command: full product strategy in 9 sections
The /strategy command builds a complete product strategy through a 9-section Canvas: vision, segments, value, trade-offs, metrics, growth, capabilities, and defensibility.
MIT ★ 28,211 updated 2026-10-16
/plugin marketplace add phuryn/pm-skills
/plugin install pm-product-strategy@pm-skillsWhat strategy does
Pass a product name, an uploaded deck or business plan, or let the command ask you about what you're building. It then works through the Strategy Canvas step by step: north star vision, who you serve and who you don't, problems you solve, value propositions framed around jobs to be done, what you deliberately choose not to build, success metrics, acquisition and expansion mechanics, core capabilities needed, and the moat that makes you hard to copy.
Each section is filled with specifics from your context, not generic guidance. The command asks clarifying questions early, then outputs a markdown document with tables, JTBD-style value propositions, and top strategic risks. The final version fits on one page for executives.
After building the canvas, the command suggests next steps: Lean Canvas, Business Model Canvas, a roadmap, macro environment scan, or OKRs tied to your north star metric.
What it helps with
- write a product strategy without generic templates
- identify and prioritize target customer segments
- articulate value propositions using Jobs to be Done
- establish strategic trade-offs and what to say no to
- define defensibility and competitive moats
Example prompts for the agent
- Build a strategy for an AI-powered design tool for non-designers
- Here's our pitch deck — walk me through the Canvas and flag gaps
- Create a Strategy Canvas for our startup, then suggest OKRs based on it
How to install strategy
1Plugin marketplace
/plugin marketplace add phuryn/pm-skills/plugin install pm-product-strategy@pm-skills2Manually: put the files in place
.claude/commands/strategy.mdCall it with /strategy. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/strategy.mdCall it with /prompts:strategy. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/strategy.prompt.mdManually: put the files in place
.gemini/commands/strategy.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about strategy
How do I install strategy in Claude Code?
Run /plugin marketplace add phuryn/pm-skills, then /plugin install pm-product-strategy@pm-skills. The command will be available as /strategy.
What does the strategy command do?
It builds a 9-section Strategy Canvas covering vision, target segments, value, propositions, trade-offs, metrics, growth engine, capabilities, and defensibility. It takes a product description or documents, asks clarifying questions, and outputs a structured markdown with tables and strategic risks.
Does it work for early-stage products?
Yes—for idea, MVP, growth, and mature stages. Early-stage sections are labeled as hypotheses. It's useful for new product launches, pivots, annual planning, and fundraising.
Source text
strategy.md · MIT
--- description: Create a comprehensive product strategy using the 9-section Strategy Canvas — from vision to defensibility argument-hint: "<product or company>" --- # /strategy -- Product Strategy Canvas Build a complete product strategy document using the 9-section Product Strategy Canvas. Covers vision, segments, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. ## Invocation ``` /strategy AI-powered design tool for non-designers /strategy [upload existing strategy doc, pitch deck, or business plan] /strategy # asks about your product ``` ## Workflow ### Step 1: Understand the Product Accept context from: - Product description (verbal or written) - Uploaded documents (strategy decks, pitch decks, PRDs, business plans) - Existing strategy to refine or challenge Ask key questions: - What does the product do? Who is it for? - What stage is it in? (idea, MVP, growth, mature) - What's the business model? - What triggered the need for a strategy document? (new product, pivot, annual planning, fundraise) ### Step 2: Build the Strategy Canvas Apply the **product-strategy** and **product-vision** skills: Work through all 9 sections of the Strategy Canvas: 1. **Vision**: Inspiring north star that motivates the team 2. **Target Segments**: Who you serve (and who you don't) 3. **Pain Points & Value**: Problems you solve and the value you create 4. **Value Propositions**: JTBD-framed value for each segment 5. **Strategic Trade-offs**: What you choose NOT to do (as important as what you do) 6. **Key Metrics**: How you measure success 7. **Growth Engine**: How you acquire and expand users 8. **Core Capabilities**: What you need to build and maintain 9. **Defensibility**: What makes this hard to copy (network effects, data, brand, switching costs) For each section, provide specific content — not generic advice. ### Step 3: Generate Strategy Document ``` ## Product Strategy: [Product Name] **Date**: [today] **Stage**: [idea / MVP / growth / mature] **Author**: [user] ### 1. Vision [Inspiring, achievable, emotional — 2-3 sentences max] ### 2. Target Segments | Segment | Size | Pain Level | Current Alternative | Priority | |---------|------|-----------|-------------------|----------| **Primary segment**: [who and why] **Explicitly not serving**: [who and why] ### 3. Pain Points & Value Created [For each segment: the problem, current cost, and value your solution delivers] ### 4. Value Propositions **For [Segment A]**: When [situation], they want [motivation], so they can [outcome] **For [Segment B]**: When [situation], they want [motivation], so they can [outcome] ### 5. Strategic Trade-offs | We Choose | Over | Because | |-----------|------|---------| ### 6. Key Metrics - **North Star**: [metric] - **Input Metrics**: [3-5 levers] - **Health Metrics**: [guardrails] ### 7. Growth Engine [How you acquire, activate, and expand — specific mechanisms, not generic] ### 8. Core Capabilities | Capability | Build / Buy / Partner | Investment Level | Timeline | |-----------|---------------------|-----------------|----------| ### 9. Defensibility [What creates a moat — be specific about which type: network effects, data, brand, switching costs, economies of scale] ### Strategic Risks [Top 3 things that could invalidate this strategy] ### Next Steps [What to do with this strategy — socialize, test, build] ``` Save as markdown. ### Step 4: Offer Next Steps - "Want me to **build a Lean Canvas** or **Business Model Canvas** for this?" - "Should I **create a roadmap** aligned to this strategy?" - "Want me to **run a macro environment scan** to stress-test assumptions?" - "Should I **define OKRs** based on Section 6?" ## Notes - A good strategy is more about what you say NO to than what you say YES to — push hard on trade-offs - Vision should be emotional and memorable, not a corporate statement - Defensibility is the hardest section — most products don't have a real moat yet, and that's OK to acknowledge - If the product is early-stage, some sections will be hypotheses — label them as such - Strategy should fit on one page for executives — offer a condensed version
© Paweł Huryn · MIT · phuryn/pm-skills
Similar slash commands
All slash commands for Notes, tasks and projects →strategy by other authors comes first.