good-strategy-bad-strategy
FeaturedFormulate and audit real strategy using Richard Rumelt's "Good Strategy Bad Strategy": an honest diagnosis, a guiding policy, and coherent action instead of goals, vision, and wishful thinking. Use when the user mentions "good strategy bad strategy", "strategy kernel", "diagnosis guiding policy coherent action", "our strategy is just goals", "strategic planning", "mission vs strategy", "annual plan", or "is this actually a strategy". Also trigger when auditing a strategy doc or pitch deck for fluff, turning a goal list into real strategy, formulating strategy for a product or company, or finding leverage and proximate objectives. Covers the kernel of strategy, bad-strategy detection, and sources of power. For product positioning, see obviously-awesome. For uncontested markets, see blue-ocean-strategy.
Install
Quality Score: 96/100
Skill Content
Details
- Author
- wondelai
- Repository
- wondelai/skills
- Created
- 7 months ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
good-strategy
Strategy evaluation and design framework based on Richard Rumelt's "Good Strategy Bad Strategy" and Michael Porter's "What Is Strategy?". Use this skill whenever the user is discussing strategy, plans, priorities, vision, roadmaps, OKRs, or competitive positioning — even if they do not explicitly say "good strategy", "Rumelt", "Porter", or "strategy kernel". Triggers include: (1) evaluating whether a strategy is good or bad, (2) diagnosing the core challenge before proposing solutions, (3) building a coherent strategy kernel (diagnosis + guiding policy + coherent actions), (4) stress-testing strategic plans with pre-mortem analysis, (5) diagnosing strategy claims that are actually goals, visions, or budgets dressed up as strategy, (6) reviewing a "strategy doc" or "strategic priorities" for fluff and incoherence, (7) applying Porter's five forces or value chain analysis, (8) deciding what to say "no" to and identifying trade-offs, (9) auditing roadmaps or resource allocation for strategic coherence.
strategy-doc
Write product strategy documents with real tradeoffs and clear choices. Use when asked to write a product strategy, define strategic direction, create a strategy doc, or articulate where to play and how to win. Built on Playing to Win and Rumelt's Strategy Kernel.
strategy-critic
Stress-test a product strategy with two explicit checks, Rumelt's kernel test and the Playing-to-Win "what would have to be true" test, plus a durability check against the seven powers. Use when a strategy draft needs review before signature, when leadership suspects it is a goals slide, when the roadmap contains bets the strategy cannot explain, or before annual planning copies last year's strategy forward. Takes the strategy document and its evidence links; returns a verdict per check, the conditions that would have to be true with their evidence status, and the rewrites needed, in the product strategy template.