Skip to main content
command CX Codex

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

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add phuryn/pm-skills
/plugin install pm-product-strategy@pm-skills
Open on GitHub

What 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-skills

2Manually: put the files in place

.claude/commands/strategy.md

Call it with /strategy. For all projects use ~/.claude/commands/

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.

strategy Gordon Mickel Generates and maintains the root STRATEGY.md file covering your project problem, approach, users, and metrics. CX Codex +1 ★ 730repo stars good-strategy-bad-strategy wondelai good-strategy-bad-strategy is a Claude Code and Codex skill for building and auditing strategy with Richard Rumelt’s framework: diagnosis, guiding policy, and coordinated action. CX Codex +1 3,600installs planning-cadence RefoundAI planning-cadence — a skill for Claude Code, Codex, Cursor and other AI coders that builds a planning system across annual, quarterly and weekly horizons. Triggers when discussing team planning processes. CX Codex +1 491installs flow-next-strategy Gordon Mickel The flow-next-strategy skill for Claude Code creates and updates STRATEGY.md at the repository root with a product’s target problem, approach, audience, metrics, and work tracks. CX Codex +1 ★ 730repo stars blue-ocean-strategy wondelai blue-ocean-strategy — a skill that walks an idea through blue ocean frameworks: strategy canvas, ERRC grid, six paths, buyer utility map. Useful when the market is crowded and you can't see a way out. CX Codex +1 5,800installs strategy-document jezweb Writes strategy documents for small and medium businesses: SWOT, lean business plan, OKRs, competitive analysis. Each mode has its own structure and quality bar. CX Codex +1 1,100installs business-strategy travisjneuman business-strategy equips your AI agent with business frameworks for competitive analysis, BCG and McKinsey matrices, market entry plans, and M&A integration. CX Codex +1 509installs

From the same set120

The whole set →
write-stories write-stories is a Claude Code command that turns a feature brief or PRD into backlog items with acceptance criteria. Choose user stories, job stories, or WWA. CX Codex +1 ★ 28,211repo stars analyze-test analyze-test is a Claude Code command that evaluates A/B test results, checks statistical significance and sample size, and recommends whether to ship, extend, or stop. CX Codex +1 ★ 28,211repo stars north-star Identifies your North Star Metric, validates it against core criteria, and outlines actionable input metrics. CX Codex +1 ★ 28,211repo stars growth-strategy growth-strategy builds a growth plan from growth loops and GTM motions. Use it when product traction stalls or you need a structured experiment plan. CX Codex +1 ★ 28,211repo stars research-users research-users synthesizes research notes, survey exports, and tickets into user personas, behavioral segments, and journey maps. Helpful for PMs evaluating qualitative data. CX Codex +1 ★ 28,211repo stars setup-metrics setup-metrics is a Claude Code command that defines product metrics from a North Star to alert thresholds. It covers feature measurement planning and dashboard reviews. CX Codex +1 ★ 28,211repo stars triage-requests triage-requests takes a batch of feature requests in any format and organizes them into themed groups ranked by priority. Helps clarify what users actually need and where to focus next. CX Codex +1 ★ 28,211repo stars plan-launch plan-launch builds a full go-to-market launch plan: from beachhead market and ICP to messaging, channel priorities, and timeline saved to Markdown. CX Codex +1 ★ 28,211repo stars

Project sponsors

Companies that keep this analytics open