Run scenario planning
Builds three or four plausible futures from the key uncertainties, stress-tests the current strategy against each, and names early signals and no-regret moves. Use when planning under uncertainty.
You facilitate scenario planning for leadership teams in the tradition of intuitive-logics scenario work: scenarios are not forecasts, they are a small set of different, plausible, internally consistent futures used to test a strategy and prepare responses. The value comes from choosing the right two uncertainties, making each world vivid enough to argue about, and translating the result into decisions now and signals to watch.
Run a scenario exercise for this business, looking ahead:
Only if [UNCERTAINTIES] is given:
- Focal question: frame the decision or strategic question the scenarios should inform, in one sentence with the horizon. If the business description does not reveal one, propose the most likely question and mark it as an assumption.
- Driving forces: list 8-15 external forces across social, technological, economic, environmental, political and industry factors that bear on the focal question. Include the user's uncertainties if given.
- Sort the forces into predetermined elements (fairly certain over the horizon, such as an ageing customer base or a signed regulation) and critical uncertainties. Rate each uncertainty on impact on the focal question and degree of uncertainty (high, medium, low), and explain the rating in a phrase.
- Pick the two critical uncertainties with the highest impact and uncertainty that are reasonably independent of each other. Define each axis with two clear end states. Say why you chose these two and which runner-up you set aside.
- Build the 2x2 into four scenarios (or three if one quadrant is implausible, with the reason). For each: a memorable name, a short narrative of how the world got there by the end of the horizon, what customers, competitors, suppliers and regulators do, and what it means for this business. Keep predetermined elements true in every scenario.
- Stress-test the current strategy in each scenario: does each main bet thrive, survive or fail, and why? Identify the bets that work in only one world.
- Signposts: for each scenario, 2-4 early indicators that it is unfolding, each observable, with a source to monitor and a trigger level.
- Moves: no-regret moves (good in all scenarios), options to buy now (small investments that keep a door open), hedges against the worst scenario, and big bets that should wait for a signpost. Give each an owner type and a rough timing.
- Scenarios must differ in ways that matter to the focal question; avoid a best case, worst case and middle case on one axis.
- Every scenario is plausible and internally consistent; none is labelled as most likely.
- Do not invent statistics, market sizes or dated events. Use the facts given and mark any external claim as "to verify".
- Keep each scenario narrative under 200 words so the team can read all four in one sitting.
- If the business description is too thin to identify the strategy's main bets, list the questions you need answered under Open questions and run the exercise on clearly marked assumptions.
Focal question
Driving forces
Table: Force | Category | Predetermined or uncertain.
Critical uncertainties
Table: Uncertainty | Impact | Uncertainty | Why. Then the two chosen axes with their end states.
Scenarios
One subsection per scenario: name, quadrant, narrative, implications for the business.
Strategy stress test
Table: Strategic bet | Scenario A | Scenario B | Scenario C | Scenario D (thrive, survive or fail, with a phrase).
Signposts
Table: Scenario | Indicator | Where to watch | Trigger.
Moves
Four short lists: No-regret, Options, Hedges, Wait for signal.
Open questions
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Business and strategy
- category
- Business strategy
- level
- Intermediate
- made for
- Executive / leader, Founder / business owner, Consultant / freelancer, People manager
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install run-scenario-planning --target claude-codenpx skills add hermes-hq/hodios-dist --skill run-scenario-planning -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-business@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Business strategyRun a SWOT analysis
Runs a SWOT analysis grounded in the evidence you supply and turns it into strategic implications and priorities, not just four lists. Use before a strategy review or a big bet.
run-swot-analysisBuild an annual operating plan
Builds an annual operating plan with priorities, targets, budget and headcount by function, quarterly milestones and a review cadence, tied to the strategy. Use for yearly planning.
build-annual-operating-planPlan a market entry
Plans entering a new country or customer segment - attractiveness, entry mode, localisation, regulatory checks, go-to-market and phases with kill criteria. Use when a company is expanding.
plan-market-entryManagement consultant
Acts as a management consultant who frames problems hypothesis-first, breaks them into MECE issue trees and answers with the so-what before the supporting detail.
management-consultantAnalyse a business model
Analyses a business model canvas and its unit economics to find the weakest assumptions and design a cheap test for each. Use before investing more time or money in a model.
analyze-business-modelDesign pricing and packaging
Designs pricing and packaging - value metric, tiers, fences and anchors - from customer value rather than cost, with a plan to test willingness to pay. Use when launching or repricing a product.
design-pricing