good-strategy-bad-strategy

Solid

Formulate 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", "review my strategy", or "annual plan". Also trigger when auditing strategy docs or pitch decks for fluff, turning goal lists into real strategy, formulating strategy for a product or company, or identifying leverage and proximate objectives. Covers the kernel of strategy, bad-strategy detection, and sources of power. For product positioning, see obviously-awesome. For creating uncontested markets, see blue-ocean-strategy.

AI & Automation 1,295 stars 135 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Good Strategy Bad Strategy A framework for creating and auditing strategy, distilled from Richard Rumelt's *Good Strategy Bad Strategy: The Difference and Why It Matters*. Good strategy has a simple underlying logic — an honest diagnosis of the critical challenge, a guiding policy for overcoming it, and coherent actions that carry the policy out. Use this skill to detect the four hallmarks of bad strategy and to replace goal lists and vision decks with a working kernel. ## Core Principle **Strategy is coherent action backed by an honest diagnosis — not goals, vision, or wishful thinking.** A goal ("20% growth") names an ambition; a strategy explains how the ambition will be achieved given the actual obstacles. Bad strategy is not the absence of strategy but an active substitute for it: buzzword fluff, refusal to name the challenge, and laundry lists of initiatives. The heart of strategy work is choice — concentrating effort and resources on the one or two pivotal objectives whose accomplishment unlocks everything else. ## Scoring **Goal: 10/10.** Rate strategies, plans, and strategy documents 0-10 against the principles below. Report the current score and the specific changes needed to reach 10/10. - **9-10:** Complete kernel — honest diagnosis, choiceful guiding policy, coordinated resource-backed actions — aimed at a pivot point, with an explicit list of what will not be done - **7-8:** Kernel present but one element weak: thin diagnosis, a policy that rules little ...

Details

Author
wondelai
Repository
wondelai/skills
Created
4 months ago
Last Updated
yesterday
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

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) distinguishing strategy from goals, ambitions, or wish lists, (6) diagnosing strategy claims that are actually just goals, visions, or budgets dressed up as strategy, (7) reviewing a "strategy doc", "strategic priorities", "strategic plan", or "strategic objectives" for fluff and incoherence, (8) evaluating Porter's five forces, value chain, or competitive positioning conversa

0 Updated 2 weeks ago
tomaszstaniak
AI & Automation Listed

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.

2 Updated today
AashutoshR2062
Code & Development Solid

strategy-review

Use when reviewing, critiquing, or stress-testing an existing strategy document. Evaluates seven dimensions — diagnosis quality, guiding policy strength, action coherence, assumption exposure, falsifiability — with optional 7S, Five Forces, Balanced Scorecard, and Hoshin Kanri lenses. Triggers on: review my strategy, poke holes in this plan, what's weak here, strategy audit, red team this. Does NOT build strategy (use strategy-interview) or brainstorm project ideas (use brainstorm-beagle).

63 Updated 2 days ago
existential-birds