Use strategy-analysis

Run a strategy framework

Run a strategy framework — SWOT/TOWS, Porter's Five Forces, or PESTLE — on a product, company, or market question, choosing the right framework for the question and forcing every cell to carry evidence and a so-what.

Reach for it when the user asks for a SWOT, a competitive/market analysis, "should we enter this market", "what's our position against X", or a macro-environment scan.

Install it

npx skilldrop-cli install strategy-analysis                 # Claude Code, your user folder
npx skilldrop-cli install strategy-analysis --project       # Claude Code, this repo
npx skilldrop-cli install strategy-analysis --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the Product manager pack: --pack product-manager installs it with its neighbours.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "Run a SWOT analysis on our product"
• "Should we enter the SMB payroll market?"
• "Do a Porter's Five Forces on the ride-sharing industry"
• "What macro trends could threaten our 3-year platform bet?"
• "Why are our margins compressing — analyze the competitive pressure"

Requests like these belong to a different skill, so it shouldn't answer them:

• "Compare Postgres vs DynamoDB for our new service"
• "Write a business case for acquiring this tooling vendor"
• "Write a PRFAQ for our new product idea"

If another skill answers instead, ask for this one by name: "use strategy-analysis".

Check what you get

A good result:

• The framework fits the question, and the doc says why in one line. A SWOT that should have been Five Forces is a category error, not a style choice.
• Every cell passes specific/evidenced/consequential. One untagged, implication-free cell is a defect; a grid of them is a horoscope.
• SWOT always arrives as TOWS. Four lists with no crossings is inventory, not strategy.
• Every Five Forces rating names the mechanism. "Rivalry: high" without who/why is a vibe with a color.
• The implications are ranked and action-shaped, tied to the named decision — not "consider monitoring the competitive landscape".
• The verdict takes a side and names what would change it. An analysis that ends "it depends" has refused its job.

See a worked example

• market entry tows

Use something else when

• Choosing between named technologies or vendors — the strategic question is already answered; compare the options directly
• A costed build/buy/defer decision — business-case
• Testing a specific product concept — prfaq
• Quarterly goal-setting — okr-cascade

Where a loop runs it

• Stage gather of the discover loop

Next

• SKILL.md, the instructions the agent reads
• Its page on the site
• Related: business-case, okr-cascade, prfaq

Edit this page on GitHub · View source