product-strategy
# ClaudeWave: product-strategy The product-strategy skill generates a comprehensive nine-section Product Strategy Canvas that systematically defines a product's competitive positioning, market targeting, value delivery, and defensibility. Use this skill when developing a new product strategy, creating a strategic plan document, refining product direction, or analyzing how a product will compete and grow in its market across dimensions including vision, target segments, costs, value propositions, trade-offs, metrics, growth model, required capabilities, and competitive defensibility.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/product-strategy && cp -r /tmp/product-strategy/pm-product-strategy/skills/product-strategy ~/.claude/skills/product-strategySKILL.md
# 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)](https://docs.google.com/presentation/d/1xRBqSOISvAKzwM_z5tC8fiuO5O2YhboB/edit?usp=sharing&ouid=111307342557889008106&rtpof=true&sd=true) --- ### Further Reading - [Product Strategy Canvas: From Vision to Action](https://www.productcompass.pm/p/product-strategy-canvas) - [Product Strategy Examples: Google Maps, Netflix, OpenAI](https://www.productcompass.pm/p/product-strategy-examples) - [Product Vision vs Strategy vs Objectives vs Roadmap: The Advanced Edition](https://www.productcompass.pm/p/product-vision-strategy-goals-and) - [Product Model First Principles: Product Team and Product Strategy In Depth](https://www.productcompass.pm/p/product-model-first-principles-transformed-cagan) - [Introducing the Product Strategy Canvas](https://www.productcompass.pm/p/new-product-strategy-canvas) - [Business Outcomes vs Product Outcomes vs Customer Outcomes](https://www.productcompass.pm/p/business-outcomes-vs-product-outcomes) - [From Strategy to Objectives Masterclass](https://www.productcompass.pm/p/product-vision-strategy-objectives-course) (video course)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze 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.
Perform 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.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm 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.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.