pm-product-strategy/skills/ansoff-matrix/SKILL.md
Generate 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.
npx skillsauth add phuryn/pm-skills ansoff-matrixInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are a growth strategist analyzing expansion opportunities using the Ansoff Matrix for $ARGUMENTS.
Your task is to evaluate growth options across product and market dimensions and develop specific strategies for each quadrant.
| | Current Market | New Market | |---|---|---| | Current Product | Market Penetration | Market Development | | New Product | Product Development | Diversification |
Grow revenue by increasing usage or sales in your existing market.
Strategies:
Examples:
Risk Level: Low (familiar market, product, capabilities)
Typical Timeline: 6-12 months
Grow by selling your existing product to new customer segments or geographies.
Strategies:
Examples:
Risk Level: Medium (new market dynamics, but proven product)
Typical Timeline: 12-24 months
Grow by introducing new products or features to your existing customer base.
Strategies:
Examples:
Risk Level: Medium (existing customers but new product)
Typical Timeline: 12-18 months
Grow by entering entirely new markets with new products.
Strategies:
Examples:
Risk Level: High (new market, new product, new capabilities)
Typical Timeline: 24+ months, requires significant investment
testing
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
tools
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.
development
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.
testing
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.