scenario-war-room

What This Skill Does

The Scenario War Room is a sophisticated analytical agent skill designed for OpenClaw that moves beyond simple, linear stress testing. Unlike traditional tools that isolate a single variable, the War Room models complex, cascading failures across an entire organizational ecosystem. By using a 6-step cascade model, it simulates how a localized failure in one department—such as losing a lead engineer—triggers a domino effect through Product, Revenue, and Cash flow. It helps leadership teams move from reactive firefighting to proactive, structured contingency planning by visualizing the potential 'death spirals' that compound adversity can create. It provides concrete, actionable hedges and early-warning triggers to interrupt negative cascades before they manifest.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/alirezarezvani/scenario-war-room

Ensure your local environment is configured to support the OpenClaw plugin architecture before running the installation.

Use Cases

• Strategic Decision Making: Evaluating the impact of large, multi-front risks like market downturns coupled with internal talent loss.
• Pre-Mortem Analysis: Testing the viability of a roadmap or funding strategy against simultaneous worst-case scenarios.
• Executive Alignment: Using the Domain Impact Mapping to force cross-functional stakeholders to visualize the downstream effects of their department's failures on other areas of the business.
• Crisis Preparedness: Moving away from static 'what-if' exercises toward dynamic, time-sensitive simulation models.

Example Prompts

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

Tips & Limitations

• Quality of Input: The model is only as accurate as your variables. When defining variables, use specific, quantified data points (e.g., '28% ARR') rather than vague statements.
• Focus on Depth: Limit variables to 3 per session to prevent model dilution. Focus on the dependencies between domains rather than just the initial shock.
• Not a Crystal Ball: This tool provides high-probability paths based on inputs; it cannot predict external black-swan events perfectly. Use the output as a guide for strategic hedging rather than a deterministic forecast.
• Interrupting Cascades: Always identify the 'interruption point' in your cascade—this is the most valuable part of the analysis, as it dictates your defensive action plan.