mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-16 22:16:52 +03:00
31 lines
2.0 KiB
Markdown
31 lines
2.0 KiB
Markdown
# Source Index — strategy-frameworks
|
|
|
|
## Provenance
|
|
|
|
This skill was adapted from the [`strategy-frameworks` material](https://github.com/magnus919/hermes-profiles/tree/867a555/skills/strategy-frameworks) in `magnus919/hermes-profiles` at commit [`867a555`](https://github.com/magnus919/hermes-profiles/commit/867a555). This repository version reorganizes the material into a host-neutral index and decision prompts. It adds no scripts or templates.
|
|
|
|
## Framework References
|
|
|
|
| Framework or topic | Reference |
|
|
|---|---|
|
|
| Objectives and key results | Andy Grove; John Doerr, *Measure What Matters* (2018) |
|
|
| Five Forces | Michael E. Porter, "How Competitive Forces Shape Strategy" (1979) |
|
|
| Value-innovation tools | W. Chan Kim and Renee Mauborgne, *Blue Ocean Strategy* (2005) |
|
|
| Ansoff Matrix | H. Igor Ansoff, "Strategies for Diversification" (1957) |
|
|
| Three Horizons | Mehrdad Baghai, Stephen Coley, and David White, *The Alchemy of Growth* (1999) |
|
|
| Growth-share matrix | Bruce Henderson and the Boston Consulting Group |
|
|
| Capital allocation and M&A | Synthesized from strategy and finance literature; use deal-specific and financial sources for decisions |
|
|
|
|
These references identify intellectual provenance. The explanations in this skill are paraphrased working prompts and should be checked against the cited work when primary-source interpretation matters.
|
|
|
|
## Current Skill Boundaries
|
|
|
|
| Skill | Use it for |
|
|
|---|---|
|
|
| `product-discovery` | Stakeholder and customer discovery, interviews, and requirements evidence |
|
|
| `product-methodology` | Product prioritization, decision records, specifications, and stakeholder communication |
|
|
| `financial-modeling` | Assumptions-led financial models, valuation scenarios, unit economics, and operating metrics |
|
|
| `technology-radar` | Technology adoption posture, build-versus-buy analysis, and architecture governance |
|
|
|
|
Strategy-frameworks organizes organizational choices across these inputs; it does not replace the specialized analysis.
|