good-strategy-bad-strategy

Formulate and audit business strategy using Rumelt's kernel of diagnosis, guiding policy, and coherent action.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/HafidJoss/Lummy --skill good-strategy-bad-strategy-hafidjoss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: good-strategy-bad-strategy
Source: https://github.com/HafidJoss/Lummy/tree/main/agent/skills/good-strategy-bad-strategy
Command: npx skills add https://github.com/HafidJoss/Lummy --skill good-strategy-bad-strategy-hafidjoss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Most strategy documents are goal lists, vision statements, and buzzword-filled decks with no honest diagnosis of the actual challenge. This Skill helps you detect bad strategy and replace it with a working kernel: an honest diagnosis, a guiding policy that rules options out, and coherent, resource-backed actions. ## Core Features & Use Cases - Strategy Auditing: Score any strategy deck, annual plan, or pitch against the four hallmarks of bad strategy (fluff, failure to face the challenge, goals mistaken for strategy, bad objectives) on a reproducible 0-10 scale. - Kernel Drafting: Write a one-page strategy kernel with a falsifiable diagnosis, a guiding policy anchored in a named asymmetry, and 3-5 coherent actions with owners, budgets, and done-tests. - Sources of Power: Apply leverage, proximate objectives, chain-link analysis, design-type strategy, focus, and advantage to find where effort is amplified. - Use Case: A leadership team brings a 34-slide annual plan full of targets and initiatives. The Skill classifies every slide, finds zero diagnosis content, reconstructs the real challenge from buried evidence, and rewrites the plan as a one-page kernel with a kill list. ## Quick Start Audit the attached strategy deck and rewrite it as a one-page kernel with a diagnosis, guiding policy, and coherent actions.

Frequently Asked Questions about good-strategy-bad-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a strategy deck for bad strategy?

Classify every slide as diagnosis, policy, action, goal, evidence, or fluff, then apply the four hallmark checklists: fluff, failure to face the challenge, goals mistaken for strategy, and bad objectives. Score the result on the 0-10 scale and write a rewrite path starting with the missing diagnosis paragraph.

What is the kernel of good strategy?

The kernel is the minimum structure of a real strategy: a diagnosis naming the critical challenge, a guiding policy that rules out whole classes of action, and coherent actions with owners, resources, and dates. A document missing any of the three is not yet a strategy.

How is a strategy different from a goal or vision?

A goal names an ambition like 20% growth; a strategy explains how it will be achieved given the actual obstacles. Vision and mission statements are identity, not strategy. The verb audit distinguishes them: ambition verbs like grow and achieve signal goals, while choice verbs like concentrate and exit signal strategy.

When should I use proximate objectives instead of long-term targets?

Use proximate objectives when ambiguity is high and teams stall on grand targets. Set targets close enough to actually hit, such as two-to-six-week ambiguity-resolving goals with one owner and a verifiable done-test, then cascade each win into the next objective.

What are the limitations of this strategy framework?

The framework requires honest evidence and willingness to choose, so it cannot fix organizations unwilling to name obstacles or kill sponsored initiatives. It also produces judgment-based outputs, meaning the diagnosis quality depends on the facts supplied and must be re-tested as conditions change.