mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-11 19:47:12 +03:00
Magnus HedemarkandGitHub
035e58d3e3
Squash-merge verified routing remediation at exact head 690f9c14b0. Required validate and paired evaluation checks passed; advisory droid review had no blocking findings.
45 lines
2.2 KiB
Markdown
45 lines
2.2 KiB
Markdown
---
|
|
name: strategy-frameworks
|
|
description: >-
|
|
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. Do not use this skill for unrelated requests; route
|
|
to the nearest named specialist.
|
|
license: MIT
|
|
metadata:
|
|
source_repo: https://github.com/magnus919/hermes-profiles
|
|
source_commit: 867a555
|
|
source_path: skills/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.
|