Back to Skills

good-strategy-bad-strategy

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", "annual plan", or "is this actually a strategy". Also trigger when auditing a strategy doc or pitch deck for fl

1,974stars197forksUpdated 8/20/2026

Security Assessment

Safe(97/100)
Security Score97/100

About good-strategy-bad-strategy

Good Strategy Bad Strategy is a framework skill for formulating and auditing real strategy, distilled from Richard Rumelt's book of the same name. It solves a pervasive problem: documents and pitch decks that pass as strategy but are actually goals, vision statements, and wishful thinking. Its core principle is that strategy is coherent action backed by an honest diagnosis, and that bad strategy is not merely the absence of strategy but an active substitute for it made of buzzword fluff, refusal to name the challenge, and laundry lists of initiatives.

The skill teaches the kernel of good strategy, a diagnosis that simplifies the critical challenge, a guiding policy that channels effort by ruling out options, and coherent actions that are coordinated and resource-backed, and it provides a reproducible scoring method. An eight-row Quick Diagnostic is walked row by row, counting how many pass to produce a 0-10 score with defined bands, along with the specific changes needed to reach 10/10. Reference files detect the four hallmarks of bad strategy (fluff, failure to face the challenge, mistaking goals for strategy, and bad strategic objectives) with concrete tests such as the plain-language restatement, the negation test, buzzword density, the verb audit, and the Monday test, and cover sources of power, case studies, and the dynamics of inertia. Before/after rewrites show how to convert goal lists into working kernels.

It targets founders, product leaders, and strategists who want to write real strategy, audit a strategy doc or pitch deck for fluff, or turn a goal list into diagnosis-guiding-policy-coherent-action. It is a benign conceptual and analytical guide with no code execution, external calls, or risky behavior.

FAQ

What framework does this skill apply?

Richard Rumelt's Good Strategy Bad Strategy, centered on the 'kernel': an honest diagnosis of the critical challenge, a guiding policy to overcome it, and coherent, coordinated, resource-backed actions. A document missing any of the three is not yet a strategy.

How does it score a strategy?

It walks an eight-row Quick Diagnostic and counts how many rows pass, mapping the count to a 0-10 score with defined bands (for example, 8 rows passing is 9-10). It reports the current score plus the specific changes needed to reach 10/10, keeping ratings reproducible run to run.

What are the hallmarks of bad strategy it detects?

Four: fluff (inflated buzzword language), failure to face the challenge (never naming the real obstacle), mistaking goals for strategy (ambitions and targets with no mechanism), and bad strategic objectives (a 'dog's dinner' wish list or 'blue sky' end-state restatements).

What tests help spot fluff and goals?

Tests include a plain-language restatement, the negation test (if negating a claim is absurd, it carries no information), buzzword density counting, the abstraction-stack check, the Monday test (what would someone do differently), and a verb audit distinguishing ambition verbs from choice verbs.

When should I use this versus a positioning framework?

Use it to formulate or audit strategy, turn goal lists into a real kernel, and find leverage and proximate objectives. The skill itself points to obviously-awesome for product positioning and blue-ocean-strategy for uncontested markets.

All Files

6 files
references/bad-strategy.md11.6 KB
View
references/case-studies.md12.6 KB
View
references/sources-of-power.md11.5 KB
View
references/kernel.md11.7 KB
View
references/dynamics-inertia.md11.4 KB
View
SKILL.md18.9 KB
View

Install good-strategy-bad-strategy

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

wondelai/skills