dotfiles/dot_config/skillshare/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 pkking/dotfiles 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
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
data-ai
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
development
Run the full autonomous engineering pipeline end-to-end (plan, work, code review, test, commit, push, open PR, watch CI, fix CI failures until green). Use only when the user explicitly requests hands-off execution of a software task and provides a feature description; do not auto-route casual conversation here.
development
Create an isolated git worktree for parallel feature work or PR review. Use when starting work that should not disturb the current checkout, or when `ce-work` or `ce-code-review` offers a worktree option.