AGENT SKILL

scenario-war-room

Cross-functional what-if modeling for cascading multi-variable scenarios. Unlike single-assumption stress testing, this models compound adversity across all business functions simultaneously. Use when facing complex risk scenarios, strategic decisions with major downside, or when the user asks 'what if X AND Y both happen?'

License 许可
MIT
所属仓库
ASoudy/AGS
最近更新
2026-05-23
Stars
★ 0
Forks
0

01 前言 Front Matter

name
scenario-war-room
license
MIT
metadata
{ "author": "Alireza Rezvani", "domain": "strategic-planning", "updated": 1772668800000, "version": "1.0.0", "category": "c-level", "frameworks": "scenario-planning", "python-tools": "scenario_modeler.py" }
description
Cross-functional what-if modeling for cascading multi-variable scenarios. Unlike single-assumption stress testing, this models compound adversity across all business functions simultaneously. Use when facing complex risk scenarios, strategic decisions with major downside, or when the user asks 'what if X AND Y both happen?'

02 资源文件 2

03 SKILL.md 正文

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:

/war-room "What if we lose our top customer AND miss the Q3 fundraise?"
/war-room "What if 3 engineers quit AND we need to ship by Q3?"
/war-room "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:

Domain Owner Models
Cash & runway CFO Burn impact, runway change, bridge options
Revenue CRO ARR gap, churn cascade risk, pipeline
Product CPO Roadmap impact, PMF risk
Engineering CTO Velocity impact, key person risk
People CHRO Attrition cascade, hiring freeze implications
Operations COO Capacity, OKR impact, process risk
Security CISO Compliance timeline risk
Market CMO CAC 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:

Scenario Definition Recovery
Base One variable hits; others don't Manageable with plan
Stress Two variables hit simultaneously Requires significant response
Severe All variables hit; full cascade Existential; 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.

Hedge Cost Impact Owner Deadline
Establish $500K credit line $5K/year Buys 3 months if churn hits CFO 60 days
12-month retention bonus for 3 key engineers $90K Locks team through fundraise CHRO 30 days
Diversify to <20% revenue concentration per customer Sales effort Reduces single-customer risk CRO 2 quarters
Compress fundraise timeline, start parallel process CEO time Closes before runways merge CEO Immediate

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 Type Primary Roles Cascade To
Revenue miss CRO, CFO CMO (pipeline), COO (cuts), CHRO (layoffs)
Key person departure CHRO, COO CTO (if eng), CRO (if sales)
Fundraise failure CFO, CEO COO (runway extension), CHRO (hiring freeze)
Security breach CISO, CTO CEO (comms), CFO (cost), CRO (customer impact)
Market shift CEO, CPO CMO (repositioning), CRO (new segments)
Competitor move CMO, CRO CPO (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

04 同仓库更多 Skills

ASoudy
ASoudy/AGS

web-typography

Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", or "typographic scale". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.

★ 0
ASoudy
ASoudy/AGS

ux-heuristics

Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "UX review", "users are confused", "heuristic evaluation", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "usability testing". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.

★ 0
ASoudy
ASoudy/AGS

traction-eos

Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "Entrepreneurial Operating System", or "business operating system". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.

★ 0
ASoudy
ASoudy/AGS

top-design

Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "premium website", "portfolio site", "scroll animations", "Awwwards quality", "brand experience", "cinematic web design", "parallax storytelling", or "agency-quality site". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.

★ 0
ASoudy
ASoudy/AGS

system-design

Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.

★ 0
ASoudy
ASoudy/AGS

storybrand-messaging

Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "messaging isnt resonating", "brand script", "StoryBrand framework", or "customer as hero". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.

★ 0