# Strategy Frameworks

> Structure organizational strategy work: strategic direction, competitive and industry analysis, growth options, capital allocation, acquisitions, and portfolio choices. Use when framing consequential choices about where to compete, how to pursue an opportunity, or how to compare strategic options.

- Skill: `theheavenlyd3mon/strategy-frameworks` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds add theheavenlyd3mon/strategy-frameworks`
- Raw SKILL.md: https://api.skillmd.com/api/skills/theheavenlyd3mon/strategy-frameworks/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- License: MIT
- Author: theheavenlyd3mon (https://skillmd.com/u/theheavenlyd3mon)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/theheavenlyd3mon/strategy-frameworks

---


# Strategy 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

1. State the decision, decision owner, constraints, and evidence available.
2. Use the relevant framework to generate questions and options, not a verdict.
3. Record assumptions, uncertainties, trade-offs, and conditions that would change the recommendation.
4. 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.

