Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Conduct scenario planning to prepare for multiple plausible futures using driving forces, uncertainty axes, and the 2x2 scenario matrix. Use this skill when the user faces high uncertainty, needs to stress-test a strategy against different futures, or prepare contingency plans — even if they say 'what if things go wrong', 'what could the future look like', 'how do we prepare for uncertainty', or 'stress-test our strategy'.
.claude/skills/asgard-ai-platform-meta-scenario-planning/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | -21% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 7% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 12% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 51% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 7% | 0% |
IRON LAW: Scenarios Are Not Predictions
Scenarios are PLAUSIBLE futures, not forecasts. The goal is NOT to predict
which future will happen, but to prepare strategies that work across
MULTIPLE possible futures. A strategy that only works in one scenario
is fragile.Step 1: Driving Forces (brainstorm 10-15)
Step 2: Select Two Axes
Step 3: Build Four Scenarios
Step 4: Strategy Testing
markdown# Scenario Planning: {Context} ## Driving Forces | Force | Impact | Uncertainty | Selected? | |-------|--------|------------|-----------| | {force} | H/M/L | H/M/L | ✓/— | ## Scenario Matrix - Axis 1: {Uncertainty A} — {endpoint 1} vs {endpoint 2} - Axis 2: {Uncertainty B} — {endpoint 1} vs {endpoint 2} | | {A: endpoint 1} | {A: endpoint 2} | |---|---|---| | **{B: endpoint 1}** | **"{Scenario Name}"**: {narrative} | **"{Scenario Name}"**: {narrative} | | **{B: endpoint 2}** | **"{Scenario Name}"**: {narrative} | **"{Scenario Name}"**: {narrative} | ## Strategy Robustness Test | Strategy | Scenario 1 | Scenario 2 | Scenario 3 | Scenario 4 | |----------|-----------|-----------|-----------|-----------| | {strategy A} | ✓/△/✗ | ✓/△/✗ | ✓/△/✗ | ✓/△/✗ | ## Robust Strategies {Strategies that work in most scenarios} ## Contingency Triggers - If {early signal}, activate {contingency plan for scenario X}
references/shell-method.md| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 48,876 | 36,660 | -25% | 1 | 1 | 0% | 8,271 | 6,437 | -22% | 0 | 0 | — |
case-02 | fail→pass | 41,637 | 26,057 | -37% | 1 | 1 | 0% | 6,670 | 5,243 | -21% | 0 | 0 | — |
case-03 | fail→fail | 50,415 | 42,976 | -15% | 1 | 1 | 0% | 8,276 | 7,747 | -6% | 0 | 0 | — |
case-04 | fail→pass | 32,422 | 25,901 | -20% | 1 | 1 | 0% | 4,274 | 4,570 | +7% | 0 | 0 | — |
case-05 | fail→fail | 23,563 | 24,794 | +5% | 1 | 1 | 0% | 3,459 | 4,744 | +37% | 0 | 0 | — |
case-06 | fail→fail | 39,214 | 22,681 | -42% | 1 | 1 | 0% | 5,076 | 4,505 | -11% | 0 | 0 | — |
case-07 | fail→pass | 30,789 | 32,325 | +5% | 1 | 1 | 0% | 5,029 | 5,620 | +12% | 0 | 0 | — |
case-08 | fail→pass | 24,439 | 30,946 | +27% | 1 | 1 | 0% | 3,777 | 5,722 | +51% | 0 | 0 | — |
case-09 | fail→pass | 26,428 | 22,788 | -14% | 1 | 1 | 0% | 4,252 | 4,534 | +7% | 0 | 0 | — |
case-10 | pass→pass | 20,464 | 19,844 | -3% | 1 | 1 | 0% | 3,299 | 4,218 | +28% | 0 | 0 | — |
case-11 | fail→fail | 24,817 | 27,011 | +9% | 1 | 1 | 0% | 3,727 | 5,230 | +40% | 0 | 0 | — |
case-12 | fail→fail | 30,041 | 27,581 | -8% | 1 | 1 | 0% | 4,438 | 5,385 | +21% | 0 | 0 | — |
case-13 | fail→fail | 40,367 | 25,618 | -37% | 1 | 1 | 0% | 6,589 | 4,993 | -24% | 0 | 0 | — |
case-14 | fail→fail | 15,553 | 27,838 | +79% | 1 | 1 | 0% | 2,047 | 4,723 | +131% | 0 | 0 | — |
case-15 | fail→pass | 47,155 | 31,932 | -32% | 1 | 1 | 0% | 7,837 | 5,840 | -25% | 0 | 0 | — |
case-16 | fail→fail | 28,060 | 26,132 | -7% | 1 | 1 | 0% | 4,489 | 4,646 | +3% | 0 | 0 | — |
case-17 | fail→fail | 34,531 | 33,033 | -4% | 1 | 1 | 0% | 5,735 | 6,403 | +12% | 0 | 0 | — |
case-18 | fail→pass | 25,079 | 23,715 | -5% | 1 | 1 | 0% | 3,812 | 4,395 | +15% | 0 | 0 | — |
case-19 | fail→fail | 22,119 | 26,175 | +18% | 1 | 1 | 0% | 2,989 | 4,627 | +55% | 0 | 0 | — |
case-20 | pass→fail | 18,503 | 51,279 | +177% | 1 | 1 | 0% | 2,646 | 8,057 | +204% | 0 | 0 | — |
case-21 | pass→pass | 27,711 | 39,314 | +42% | 1 | 1 | 0% | 4,301 | 6,526 | +52% | 0 | 0 | — |
case-22 | pass→fail | 27,676 | 35,722 | +29% | 1 | 1 | 0% | 4,372 | 6,388 | +46% | 0 | 0 | — |
case-23 | pass→fail | 15,149 | 21,038 | +39% | 1 | 1 | 0% | 2,435 | 4,434 | +82% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 23 cases were attempted. The headline lift of +17 percentage points is the difference between those two pass rates over the 23 comparable cases. 3 cases got worse with the skill loaded, and they are included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.