SkillAgentSearch skills...

scenario-war-room

Cross-functional what-if modeling for compound adversity -- shows how one problem cascades into the next

Install / Use

npx skills add borghei/Claude-Skills --skill scenario-war-room

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Universal

Our assessment of scenario-war-room

scenario-war-room scores 89/100 on our quality scale, 1713th of 4,702 Development & Engineering skills we index (top 37%).

Its SKILL.md is 19 KB long, well organised into 24 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so scenario-war-room is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

scenario-war-room compared with similar skills

All 4 of these similar skills score higher than scenario-war-room; compare them before choosing.

SkillScoreStarsUpdatedFormat
scenario-war-room (this skill)by borghei8981757d agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.9k8d agoCLAUDE.md

Frequently asked questions

How do I install scenario-war-room?
Run npx skills add borghei/Claude-Skills --skill scenario-war-room. The install tabs above show the steps for each supported agent.
Which AI agents does scenario-war-room work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is scenario-war-room safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is scenario-war-room still maintained?
The repository was last updated about 2 months ago, so scenario-war-room is actively maintained.

name: scenario-war-room description: > Cross-functional what-if modeling for compound adversity -- shows how one problem cascades into the next. Use when facing complex risk scenarios, strategic decisions with major downside, or multi-variable threats. license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: c-level domain: strategic-planning tier: POWERFUL updated: 2026-03-09 frameworks: cascade-modeling, scenario-planning, pre-mortem, contingency-design

Scenario War Room

Tier: POWERFUL Category: C-Level Advisory Tags: scenario planning, war room, risk modeling, cascade effects, contingency planning, pre-mortem, crisis simulation

Overview

The Scenario War Room models cascading what-if scenarios across all business functions. Not single-assumption stress tests -- compound adversity that shows how one problem creates the next, and where the cascade can be interrupted. Every scenario produces concrete hedges with costs, owners, and deadlines.


When to Use

  • A major risk has probability above 15% and impact above 20% of ARR
  • Two or more threats could plausibly co-occur
  • A strategic decision has significant downside if wrong
  • Board or investors are asking "what's the worst case?"
  • Pre-mortem before a major commitment (fundraise, acquisition, market entry)
  • Quarterly risk review for leadership team

When NOT to Use

  • Single-variable financial sensitivity analysis (use CFO Advisor stress testing)
  • Routine project risk assessment (use project management risk frameworks)
  • Technical failure mode analysis (use engineering incident planning)

Clarify First

Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • [ ] The (maximum 3) variables that actually keep leadership awake — the entire model is built around these; the wrong variables produce a useless scenario
  • [ ] Probability, timeline, and quantified impact for each variable — "revenue drops" is not actionable; "$420K ARR at risk over 60 days" is, and severity levels depend on it
  • [ ] Current baseline (ARR, runway in months, headcount) — cascade and severity math (e.g., runway going 14→8 months) requires the starting numbers
  • [ ] Company stage — common scenario patterns and what counts as existential differ by stage

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.


The 6-Step Cascade Model

Step 1: Define Scenario Variables (Maximum 3)

More than 3 variables creates analysis paralysis, not insight. Choose the 3 that actually keep leadership awake at night.

For each variable, specify:

| Field | Description | Example | |-------|-----------|---------| | What changes | Specific, quantified | "Top customer (28% of ARR) gives 60-day termination notice" | | Probability | Your best estimate | 15% | | Timeline | When it could hit | Within 90 days | | Detection signal | How you would know it is happening | Sponsor goes dark, usage drops 25% MoM |

Variable Template:

Variable A: [Specific change]
  Probability: [X]%  |  Timeline: [When]
  Detection: [Early warning signal]
  First-order impact: [Immediate consequence]

Variable B: [Specific change]
  Probability: [X]%  |  Timeline: [When]
  Detection: [Early warning signal]
  First-order impact: [Immediate consequence]

Variable C: [Specific change]
  Probability: [X]%  |  Timeline: [When]
  Detection: [Early warning signal]
  First-order impact: [Immediate consequence]

Step 2: Domain Impact Mapping

For each variable, assess impact across every business function:

| Domain | Key Questions | Typical Impact Areas | |--------|-------------|---------------------| | Finance (CFO) | Burn impact? Runway change? Bridge options? | Cash, runway, covenant triggers | | Revenue (CRO) | ARR gap? Churn cascade? Pipeline affected? | NRR, expansion, new logo risk | | Product (CPO) | Roadmap derailed? PMF at risk? Customer need shift? | Delivery timeline, feature priority | | Engineering (CTO) | Velocity hit? Key person risk? Technical debt impact? | Capacity, architecture, hiring | | People (CHRO) | Attrition cascade? Hiring freeze? Morale impact? | Retention, culture, bench strength | | Operations (COO) | Capacity affected? Process breaks? OKR impact? | SLAs, efficiency, scale | | Market (CMO) | CAC affected? Competitive exposure? Brand risk? | Pipeline generation, positioning | | Legal/Compliance | Regulatory timeline risk? Contract exposure? | Obligations, deadlines, penalties |

Step 3: Cascade Mapping (The Core)

This is the most valuable step. Map how Variable A triggers consequences that amplify Variable B.

Cascade Diagram:

TRIGGER: Customer churn ($560K ARR)
  │
  ├──▶ CFO: Runway drops 14 → 8 months
  │     │
  │     └──▶ CHRO: Hiring freeze imposed
  │           │
  │           └──▶ CTO: 3 open engineering reqs frozen, roadmap slips 2 months
  │                 │
  │                 └──▶ CPO: Q4 feature launch delayed → 2 more customers at risk
  │                       │
  │                       └──▶ CRO: NRR drops → additional churn risk (DEATH SPIRAL ENTRY)
  │
  └──▶ CRO: Revenue concentration increases (next largest = 22%)
        │
        └──▶ Investors: Concentration risk flagged → Series A terms worsen

Name the cascades explicitly. Common cascade patterns:

| Cascade Pattern | Description | Interruption Point | |----------------|-------------|-------------------| | Revenue-to-Runway Death Spiral | Customer churn → lower runway → hiring freeze → slower product → more churn | Emergency revenue diversification | | Key Person Cascade | Star leaves → team morale drops → followers leave → velocity collapses | Retention bonuses before departure | | Market Squeeze | Competitor raises → price war → margins compress → can't invest in product | Differentiation, not price matching | | Trust Cascade | Incident → customer concern → churn → press → more churn | Swift, transparent communication | | Fundraise-Burn Spiral | Miss target → raise delayed → bridge at bad terms → burn cuts → team loss | Parallel fundraise tracks |

Step 4: Severity Matrix

Model three scenarios with increasing severity:

| Scenario | Variables Hit | Definition | Recovery Difficulty | |----------|-------------|-----------|-------------------| | Base | 1 of 3 | Single shock, others don't materialize | Manageable with prepared response | | Stress | 2 of 3 | Compound shock, cascade begins | Requires significant pivot, board involvement | | Severe | All 3 | Full cascade, existential territory | Requires emergency action, may need board intervention |

For each severity level, quantify:

BASE SCENARIO (Variable A only):
  Runway impact: [X] months → [Y] months
  ARR impact: -$[X] ([Y]% of total)
  Headcount impact: [freeze / reduction / none]
  Timeline to critical: [X] months
  Recovery plan: [specific actions]

STRESS SCENARIO (Variables A + B):
  Runway impact: [X] months → [Y] months
  ARR impact: -$[X] ([Y]% of total)
  Headcount impact: [specifics]
  Timeline to critical: [X] months
  Recovery plan: [specific actions]

SEVERE SCENARIO (All three):
  Runway impact: [X] months → [Y] months
  ARR impact: -$[X] ([Y]% of total)
  Headcount impact: [specifics]
  Timeline to critical: [X] months
  Existential: [yes/no]
  Emergency plan: [specific actions requiring board approval]

Step 5: Early Warning Signals (Trigger Points)

Define measurable signals that tell you a scenario is unfolding BEFORE it is confirmed. The value of this exercise is acting early, not reacting late.

Signal Design Criteria:

  • Observable (you can actually measure it)
  • Leading (appears before the full impact)
  • Specific (not just "things feel off")
  • Actionable (triggers a specific response)

| Variable | Signal | Threshold | Response | |----------|--------|-----------|----------| | Customer churn | Sponsor stops responding | > 3 weeks silence | Exec escalation, QBR request | | Customer churn | Usage drops | > 25% MoM decline | CS outreach, value review | | Fundraise delay | Term sheets | < 3 after 60 days in process | Parallel bridge conversations | | Fundraise delay | Investor requests | > 30 day DD extension | Reduce burn, extend runway | | Key person departure | Market compensation | Counter-offer required in last 90 days | Retention package, succession plan | | Key person departure | External engagement | Engineer presenting at conferences for competitors | Direct conversation, role expansion |

Step 6: Hedging Strategies

For each scenario: actions to take NOW (before the scenario materializes) that reduce impact if it does. Hedges have costs -- the goal is cheap insurance, not paranoia.

Hedge Evaluation Criteria:

| Criterion | Question | |-----------|----------| | Cost | What does this hedge cost to implement? | | Reversibility | Can we undo it if the scenario doesn't happen? | | Lead time | How long to implement? (Must be shorter than detection-to-impact window) | | Coverage | Which scenarios does this hedge protect against? | | Side effects | Does this hedge cause other problems? |

Hedge Table Template:

| Hedge | Cost | Protects Against | Owner | Deadline | Status | |-------|------|-----------------|-------|----------|--------| | Establish $500K credit line | $5K/year | Runway shortfall (Base + Stress) | CFO | 60 days | Not started | | 12-month retention bonus for 3 key engineers | $90K | Key person departure (all scenarios) | CHRO | 30 days | In progress | | Diversify to <20% revenue per customer | Sales effort (6 months) | Single-customer dependency | CRO | 2 quarters | Planning | | Start parallel fundraise track | CEO time (10 hrs/week) | Fundraise delay (Stress + Severe) | CEO | Immediate | Not started | | Pre-negotiate bridge terms with existing investors | 2 board conversations | Runway crisis (Severe) | CFO + CEO | 45 days | Not started | | Document architecture for bus factor reduction | 2 engineering weeks | Key person departure | CTO | 30 days | Not started |


Output Format

Every war room session produces this structured output:

SCENARIO: [Name]
DATE: [Date of analysis]
PARTICIPANTS: [Who was involved]

VARIABLES:
  A: [Description] — Probability: [X]%, Timeline: [When]
  B: [Description] — Probability: [X]%, Timeline: [When]
  C: [Description] — Probability: [X]%, Timeline: [When]

MOST LIKELY PATH: [Which combination actually plays out, with reasoning]

SEVERITY LEVELS:
  Base (A only):  Runway [X]→[Y]mo, ARR impact -$[X]
    Recovery: [2-3 specific actions]
  Stress (A+B):   Runway [X]→[Y]mo, ARR impact -$[X]
    Recovery: [3-4 specific actions]
  Severe (A+B+C): Runway [X]→[Y]mo, ARR impact -$[X]
    Existential: [yes/no]
    Emergency: [actions requiring board approval]

CASCADE MAP:
  [A] → [domain impact] → [triggers B amplification] → [domain impact] → [end state]
  Interruption points: [where cascade can be broken]

EARLY WARNING SIGNALS:
  1. [Signal] → indicates [scenario], threshold: [specific]
  2. [Signal] → indicates [scenario], threshold: [specific]
  3. [Signal] → indicates [scenario], threshold: [specific]

HEDGES (implement now):
  1. [Action] — cost: $[X] — protects: [scenarios] — owner: [role] — deadline: [date]
  2. [Action] — cost: $[X] — protects: [scenarios] — owner: [role] — deadline: [date]
  3. [Action] — cost: $[X] — protects: [scenarios] — owner: [role] — deadline: [date]

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

REVIEW DATE: [When to re-run this analysis — typically 90 days or after any variable shifts]

Common Scenarios by Company Stage

Seed Stage

  • Co-founder departure + product misses launch deadline
  • Runway runs out + bridge terms are predatory
  • Key technical hire falls through + competitor ships first

Series A

  • Miss ARR tar

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars817
CategoryDevelopment
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium