← Back to list
⚡

product-strategy Checked

Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, seg…
⚡ Productivity skills By phuryn Version v1.0.0 Added 2026-09-03 Updated 2026-09-03 Source ↗
7.6Overall rating
2Views
6Downloads
26.0kStars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "product-strategy" skill by following the instructions at https://skill123.me/install/product-strategy.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/product-strategy.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 2 KB
📊 Static rating
7.6/10
Trigger
7.0
Structure
7.3
Workflow
7.2
Content
8.0
Engineering
6.0
Security
9.5

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

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.

Product Strategy Canvas

Documentation

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.

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?
View full documentation

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

---

### Further Reading

Score breakdown

Trigger
7.0
Good What and When with strategy-canvas triggers in body, but no explicit exclusions.
Structure
7.3
111-line single file with redundant Metadata block duplicating frontmatter; template is question-driven.
Workflow
7.2
Twelve-step output process with strategy coherence validation, critical hypotheses, and low-effort experiments.
Content
8.0
Clear canvas questions and notes; some sections are prompts rather than executable instructions.
Engineering
6.0
Valid frontmatter; external PPTX template on docs.google.com and credible article links.
Security
9.5
No scripts, no injection or secrets; external links on official Google and PM blog domains.
Well-organized 9-section strategy canvas with a 12-step process including coherence checks and validation experiments, but body duplicates frontmatter metadata and offers no When-Not boundary.