Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alirezarezvani avatar

Scenario War Room

  • 527 installs
  • 23.5k repo stars
  • Updated July 17, 2026
  • alirezarezvani/claude-skills

scenario-war-room is a Claude Code skill that facilitates structured scenario-planning sessions using Shell-style 2x2 matrices to stress-test product and strategy assumptions before commitment.

About

Scenario War Room is an agent skill that equips developers with Shell's classic scenario planning framework and Monte Carlo mental models. Instead of treating the future as a single forecast, it forces you to explore four distinct, named futures created from two critical uncertainties. The skill guides you through identifying predetermined elements that will happen anyway, spotting early indicators you can monitor today, and running lightweight Monte Carlo simulations on 3-5 key variables. The included startup 2x2 matrix (raise successfully vs bridge, fast vs slow market growth) gives immediate traction while the methodology works for any major decision. Developers use it to pressure-test roadmaps, pricing, hiring, and positioning long before writing the first line of code or raising capital.

  • Adapts Shell's 1970s scenario planning methodology for solo founders and indie builders
  • Uses 2x2 matrix built from two critical uncertainties to generate four mutually exclusive scenarios
  • Includes named scenarios, predetermined elements, and early warning indicators for each quadrant
  • Combines Monte Carlo mental model with 3-5 key variables to quantify outcome distributions
  • Provides ready-to-use 2x2 startup matrix for fundraising vs market-growth uncertainties

Scenario War Room by the numbers

  • 527 all-time installs (skills.sh)
  • +4 installs in the week ending Jun 18, 2026 (Skillselion tracking)
  • Ranked #733 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill scenario-war-room

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs527
repo stars23.5k
Security audit2 / 3 scanners passed
Last updatedJuly 17, 2026
Repositoryalirezarezvani/claude-skills

How do you run scenario planning for product strategy?

Run structured scenario-planning sessions that stress-test assumptions before committing to product direction or strategy.

Who is it for?

Product managers and tech leads facing high uncertainty who need facilitated scenario workshops before committing to a single roadmap.

Skip if: Near-term sprint planning, deterministic revenue forecasting, or teams seeking a single approved forecast rather than exploratory futures.

When should I use this skill?

A team debates strategic direction, faces regulatory or technology uncertainty, or asks for scenario planning or war-room facilitation.

What you get

Named 2x2 scenario matrix, critical uncertainty map, predetermined-elements list, and strategy implications per quadrant.

  • 2x2 scenario matrix
  • Named future scenarios
  • Predetermined-elements inventory

Files

SKILL.mdMarkdownGitHub ↗

Scenario War Room

Model cascading what-if scenarios across all business functions. Not single-assumption stress tests — compound adversity that shows how one problem creates the next.

Keywords

scenario planning, war room, what-if analysis, risk modeling, cascading effects, compound risk, adversity planning, contingency planning, stress test, crisis planning, multi-variable scenario, pre-mortem

Quick Start

python scripts/scenario_modeler.py   # Interactive scenario builder with cascade modeling

Or describe the scenario in natural language:

"What if we lose our top customer AND miss the Q3 fundraise?"
"What if 3 engineers quit AND we need to ship by Q3?"
"What if our market shrinks 30% AND a competitor raises $50M?"

What This Is Not

  • Not a single-assumption stress test (that's /em:stress-test)
  • Not financial modeling only — every function gets modeled
  • Not worst-case-only — models 3 severity levels
  • Not paralysis by analysis — outputs concrete hedges and triggers

Framework: 6-Step Cascade Model

Step 1: Define Scenario Variables (max 3)

State each variable with:

  • What changes — specific, quantified if possible
  • Probability — your best estimate
  • Timeline — when it hits
Variable A: Top customer (28% ARR) gives 60-day termination notice
  Probability: 15% | Timeline: Within 90 days

Variable B: Series A fundraise delayed 6 months beyond target close
  Probability: 25% | Timeline: Q3

Variable C: Lead engineer resigns
  Probability: 20% | Timeline: Unknown

Step 2: Domain Impact Mapping

For each variable, each relevant role models impact:

DomainOwnerModels
Cash & runwayCFOBurn impact, runway change, bridge options
RevenueCROARR gap, churn cascade risk, pipeline
ProductCPORoadmap impact, PMF risk
EngineeringCTOVelocity impact, key person risk
PeopleCHROAttrition cascade, hiring freeze implications
OperationsCOOCapacity, OKR impact, process risk
SecurityCISOCompliance timeline risk
MarketCMOCAC impact, competitive exposure

Step 3: Cascade Effect Mapping

This is the core. Show how Variable A triggers consequences in domains that trigger Variable B's effects:

TRIGGER: Customer churn ($560K ARR)
  ↓
CFO: Runway drops 14 → 8 months
  ↓
CHRO: Hiring freeze; retention risk increases (morale hit)
  ↓
CTO: 3 open engineering reqs frozen; roadmap slips
  ↓
CPO: Q4 feature launch delayed → customer retention risk
  ↓
CRO: NRR drops; existing accounts see reduced velocity → more churn risk
  ↓
CFO: [Secondary cascade — potential death spiral if not interrupted]

Name the cascade explicitly. Show where it can be interrupted.

Step 4: Severity Matrix

Model three scenarios:

ScenarioDefinitionRecovery
BaseOne variable hits; others don'tManageable with plan
StressTwo variables hit simultaneouslyRequires significant response
SevereAll variables hit; full cascadeExistential; requires board intervention

For each severity level:

  • Runway impact
  • ARR impact
  • Headcount impact
  • Timeline to unacceptable state (trigger point)

Step 5: Trigger Points (Early Warning Signals)

Define the measurable signal that tells you a scenario is unfolding before it's confirmed:

Trigger for Customer Churn Risk:
  - Sponsor goes dark for >3 weeks
  - Usage drops >25% MoM
  - No Q1 QBR confirmed by Dec 1

Trigger for Fundraise Delay:
  - <3 term sheets after 60 days of process
  - Lead investor requests >30-day extension on DD
  - Competitor raises at lower valuation (market signal)

Trigger for Engineering Attrition:
  - Glassdoor activity from engineering team
  - 2+ referral interview requests from engineers
  - Above-market offer counter-required in last 3 months

Step 6: Hedging Strategies

For each scenario: actions to take now (before the scenario materializes) that reduce impact if it does.

HedgeCostImpactOwnerDeadline
Establish $500K credit line$5K/yearBuys 3 months if churn hitsCFO60 days
12-month retention bonus for 3 key engineers$90KLocks team through fundraiseCHRO30 days
Diversify to <20% revenue concentration per customerSales effortReduces single-customer riskCRO2 quarters
Compress fundraise timeline, start parallel processCEO timeCloses before runways mergeCEOImmediate

---

Output Format

Every war room session produces:

SCENARIO: [Name]
Variables: [A, B, C]
Most likely path: [which combination actually plays out, with probability]

SEVERITY LEVELS
Base (A only): [runway/ARR impact] — recovery: [X actions]
Stress (A+B): [runway/ARR impact] — recovery: [X actions]
Severe (A+B+C): [runway/ARR impact] — existential risk: [yes/no]

CASCADE MAP
[A → domain impact → B trigger → domain impact → end state]

EARLY WARNING SIGNALS
- [Signal 1 → which scenario it indicates]
- [Signal 2 → which scenario it indicates]
- [Signal 3 → which scenario it indicates]

HEDGES (take these actions now)
1. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]
2. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]
3. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]

RECOMMENDED DECISION
[One paragraph. What to do, in what order, and why.]

---

Rules for Good War Room Sessions

Max 3 variables per scenario. More than 3 is noise — you can't meaningfully prepare for 5-variable collapse. Model the 3 that actually worry you.

Quantify or estimate. "Revenue drops" is not useful. "$420K ARR at risk over 60 days" is. Use ranges if uncertain.

Don't stop at first-order effects. The damage is always in the cascade, not the initial hit.

Model recovery, not just impact. Every scenario should have a "what we do" path.

Separate base case from sensitivity. Don't conflate "what probably happens" with "what could happen."

Don't over-model. 3-4 scenarios per planning cycle is the right number. More creates analysis paralysis.

---

Common Scenarios by Stage

Seed:

  • Co-founder leaves + product misses launch
  • Funding runs out + bridge terms unfavorable

Series A:

  • Miss ARR target + fundraise delayed
  • Key customer churns + competitor raises

Series B:

  • Market contraction + burn multiple spikes
  • Lead investor wants pivot + team resists

Integration with C-Suite Roles

Scenario TypePrimary RolesCascade To
Revenue missCRO, CFOCMO (pipeline), COO (cuts), CHRO (layoffs)
Key person departureCHRO, COOCTO (if eng), CRO (if sales)
Fundraise failureCFO, CEOCOO (runway extension), CHRO (hiring freeze)
Security breachCISO, CTOCEO (comms), CFO (cost), CRO (customer impact)
Market shiftCEO, CPOCMO (repositioning), CRO (new segments)
Competitor moveCMO, CROCPO (roadmap response), CEO (strategy)

References

  • references/scenario-planning.md — Shell methodology, pre-mortem, Monte Carlo, cascade frameworks
  • scripts/scenario_modeler.py — CLI tool for structured scenario modeling

Related skills

FAQ

What methodology does scenario-war-room follow?

scenario-war-room follows Shell-style scenario planning: pick two critical uncertainties, cross them in a 2x2 matrix, name each quadrant, and treat scenarios as thinking tools rather than forecasts.

How many scenarios does scenario-war-room typically produce?

scenario-war-room uses a 2x2 matrix across two critical uncertainties, yielding four mutually exclusive, collectively exhaustive named scenarios plus a list of predetermined elements.

Is Scenario War Room safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.