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'.
npx skills add https://github.com/asgard-ai-platform/skills --skill meta-scenario-planning
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
# 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.mdGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take asgard-ai-platform/meta-scenario-planning from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.