plugins/executive/skills/strategy-clarity/SKILL.md
Use when an organization needs strategic clarity — identifying where to play, how to win, and whether the position is defensible. Composes Wardley evolution mapping, Lafley's choice cascade, Helmer's 7 Powers, and Working Backwards based on what's already decided.
npx skillsauth add joellewis/skill-library strategy-clarityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Strategy clarity is the process of defining a coordinated set of choices that uniquely position an organization to win. This skill composes four frameworks into a pipeline: Wardley evolution mapping builds situational awareness, Lafley's cascade makes the choices, Helmer's 7 Powers stress-tests defensibility, and Working Backwards translates intent into execution. The Lafley cascade is the default and core process; the others compose around it based on what's already decided.
Strategic clarity is not a single framework — it is a pipeline of frameworks, each handling a different phase. Your entry point depends on what's already decided:
What's already decided determines where you start:
Nothing — greenfield, pivot, or "we don't know where to play"
Start with evolution mapping to build situational awareness before choosing.
→ Read references/evolution-mapping.md, then return here for the Cascade.
Where to play is clear, how to win isn't Start with the Strategic Choice Cascade below (Step 3: How to Win).
Strategy is chosen, unsure if it's defensible
Stress-test the position for durable power sources.
→ Read references/seven-powers-audit.md.
Strategy is validated, need execution machinery
Translate strategic intent into customer-facing artifacts.
→ Read references/working-backwards-execution.md.
Each phase validates the previous one's output. If the Lafley cascade produces a vague position ("be the best platform"), loop back to evolution mapping. If 7 Powers finds no defensible power source, loop back to How to Win.
Organizational commitment. This skill covers strategic choice, not organizational adoption. Securing institutional commitment for a strategy — coalition-building, guiding policy, coherent action — is a distinct challenge not covered here. (See: Rumelt, Good Strategy Bad Strategy; Kotter, Leading Change.)
Strategy is not a goal or a vision; it is a coordinated set of choices that uniquely positions the firm. If you haven't made a choice about where not to play, you don't have a strategy.
Every successful business is a monopoly by solving a unique problem. Competition is a destructive force that competes away profits. Your strategy must aim for 0-to-1 vertical progress, not 1-to-n horizontal copying.
A true platform's value is defined by the economic value created by third parties exceeding the value of the platform itself. Strategic clarity requires knowing if you are an Aggregator (owning the user) or a Platform (empowering the ecosystem).
Strategy is not what you can build, but what the customer needs you to build. All strategic logic must be validated by a "Working Backwards" PR/FAQ that proves the future state is compelling.
Great companies are built on a "secret"—a truth that very few people agree with. Strategic clarity requires identifying this contrarian insight and building a moat around it.
Identify the core purpose of the enterprise and the specific "Winning" state. (Source: Lafley, Ch. 2)
Define the specific field of play. (Source: Lafley, Ch. 3)
Define the unique value proposition. (Source: Lafley, Ch. 4)
Identify the 3-5 activities that must be performed at a high level to execute the HTW. (Source: Lafley, Ch. 5)
Ask: "What must be true about the market, customers, and competitors for this strategy to be a great idea?" (Source: Lafley, Ch. 7)
non-fiction-precision — Strategy must be communicated with absolute clarity (Pyramid Principle).mental-model-library — Use first principles and second-order thinking to validate strategic "Secrets."devils-advocate — Stress-test the "What must be true" assumptions.databases
Use when a deliverable needs structured stakeholder sign-off before finalization—runs the pre-read, feedback-type alignment, and conflict-resolution protocol.
development
Use when you need to map who has power, who will be affected, and what motivates each party — produces a stakeholder map as an analytical artifact. This skill identifies and categorizes stakeholders; it does not persuade or influence them (use influence-architect for that).
testing
Use when beginning analytical or strategic tasks, facing undefined problems, or facing analysis paralysis—requires explicit problem definition before proceeding.
testing
Use when translating a product vision into engineering requirements—enforces the Working Backwards PR/FAQ method, requiring a customer-facing press release before any technical spec.