Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold, before a large irreversible commitment, or when a market, regulatory, or technology shift could invalidate the strategy.
npx skills add https://github.com/cbrock84/headcount --skill scenario-planning
Forecasting produces one number and false confidence. Scenario planning produces a plan that
survives being wrong, which is the realistic goal.
List the plan's assumptions explicitly, then sort them:
technology already deployed. Plan around them; do not spend analysis on them.
resolve.
Almost every plan has two or three load-bearing uncertainties. Finding them is most of the
value, and the exercise usually surfaces one nobody had articulated.
The common failure is three scenarios named optimistic, base, and pessimistic — which is one scenario
with the numbers scaled, and it teaches nothing.
Take the two most consequential uncertainties and build the quadrants. Each scenario should be
internally coherent: if demand is high *and* supply is constrained, what else follows — pricing,
competitor behavior, regulatory attention?
Give each a name that captures its logic. Names make scenarios usable in conversation, which is where
they earn their keep.
Three or four scenarios. More cannot be held in mind; two collapses into best and worst.
For every scenario: does the plan still work, what breaks first, and what would we wish we had done
sooner?
The output is not a prediction. It is three things:
they look like indecision and are actually the cheapest way to handle uncertainty.
For each scenario, name the observable signal that would show it is arriving — and specify it
precisely enough to be checked. "Regulatory pressure increases" is not observable. "A second
jurisdiction opens a consultation" is.
Assign each indicator an owner and a review cadence. Scenario work that produces no monitoring is a
workshop, not a plan.
Most scenario planning is done once and filed. Its value comes from being revisited when an indicator
fires — that is the moment the earlier thinking pays, because the options were identified before
anyone was under pressure.
extra steps.
credibility.
Take cbrock84/scenario-planning from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.