About strategy-frameworks
A decision-support skill that helps teams choose strategy frameworks for the question at hand. It structures decisions around options, evidence, assumptions, uncertainty, and trade-offs rather than treating a framework as a verdict.
Key features
- 01Select references by decision type
- 02Make assumptions and alternatives explicit
- 03Record evidence and uncertainty
- 04Document trade-offs and validation steps
Use cases
- 01Develop strategic direction or OKRs
- 02Assess industry structure and positioning
- 03Compare growth or market-entry options
- 04Evaluate capital allocation or acquisitions
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/strategy-frameworksin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
README.mdevals/evals.jsonreferences/competitive-analysis.mdgrowth-strategy.mdresource-allocation.mdsource-index.mdstrategic-planning.mdDetails
From the project READMEStrategy Frameworks
Use a framework to make assumptions, alternatives, evidence, and trade-offs visible. Select a reference for the decision at hand rather than applying every framework.
| Need | Load |
|---|---|
| Direction, OKRs, values, or a narrative | references/strategic-planning.md |
| Industry structure, positioning, or potential advantages | references/competitive-analysis.md |
| Growth options, maturity states, or market entry | references/growth-strategy.md |
| Capital choices, acquisitions, or a business portfolio | references/resource-allocation.md |
| Provenance and catalog boundaries | references/source-index.md |
Working Method
- State the decision, decision owner, constraints, and evidence available.
- Use the relevant framework to generate questions and options, not a verdict.
- Record assumptions, uncertainties, trade-offs, and conditions that would change the recommendation.
- Pair strategic logic with appropriate financial, customer, technical, legal, or operational analysis.
When Not to Use
- For stakeholder interviews and raw requirement discovery, use
product-discovery. - For feature prioritization, specifications, and product communications, use
product-methodology. - For quantitative scenarios, valuation, unit economics, or capital-model calculations, use
financial-modeling. - For technology adoption posture and architecture governance, use
technology-radar.
Completion
Stop when the artifact names the decision, alternatives, evidence, key assumptions, trade-offs, and next validation or decision step. It should not present a framework classification as a prediction or decision by itself.