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.

Jump to install

Repository: magnus919/agent-skills
Last source activity: August 3, 2026 at 20:15
Detected SKILL.md language: English
Stars: 64
Forks: 7

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/magnus919/agent-skills --skill strategy-frameworks

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

8 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

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

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.