mcpbeat Sign in

Meta Scenario Planning Agent Skill

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'.

8k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
223
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/asgard-ai-platform/skills --skill meta-scenario-planning

What comes with it

27 606 bytes besides the instruction
examples/sample_scenario.md
references/shell-method.md

The instruction itself

7 sections, as written by the author

Scenario Planning

Framework

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.

The 2×2 Scenario Matrix Method

  • Identify driving forces: What macro-forces will most shape the future? (technology, regulation, economy, demographics, competition)
  • Select two critical uncertainties: The two most impactful forces with the most uncertain outcomes
  • Build the 2×2 matrix: Each axis is one uncertainty with two endpoints (e.g., "regulation: strict vs lax")
  • Name and describe four scenarios: Each quadrant is a distinct plausible future
  • Test strategies against all four: Which strategies work in most/all scenarios? Which only work in one?

Process

Step 1: Driving Forces (brainstorm 10-15)

  • Political, economic, social, technological, environmental, competitive
  • Rate each on: Impact (H/M/L) × Uncertainty (H/M/L)
  • High Impact + High Uncertainty → candidate for axes

Step 2: Select Two Axes

  • Choose two forces that are both high-impact AND high-uncertainty
  • They should be independent of each other (not correlated)

Step 3: Build Four Scenarios

  • Give each scenario a memorable name (not "Scenario 1")
  • Write a 1-paragraph narrative for each: what does this world look like in 5-10 years?

Step 4: Strategy Testing

  • For each strategy option, assess: does it work in this scenario? (Yes / Partial / No)
  • Robust strategies work in 3-4 scenarios. Fragile strategies work in only 1.

Output Format

# 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}

Gotchas

  • Scenarios should be uncomfortable: If all four scenarios are comfortable, you haven't explored enough uncertainty. Include at least one scenario you'd rather not think about.
  • Avoid "good/bad" framing: Scenarios aren't optimistic vs pessimistic. Each scenario has opportunities AND threats. A "strict regulation" world is bad for some and good for others.
  • Early warning signals: Identify observable indicators that signal which scenario is unfolding. This converts scenarios into actionable intelligence.
  • Two axes is a simplification: Reality has many uncertainties. The 2×2 is a tool for clarity, not completeness. Consider additional driving forces as variations within scenarios.

References

  • For Shell's original scenario planning methodology, see references/shell-method.md

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide 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.

4k tokens
File Organizer
by frostant
×10

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.

3k tokens
Domain Name Brainstormer
by frostant
×8

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.

1k tokens
Brainstorming
by ZhanlinCui
×4

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.

626 tokens
Planning With Files
by ZhanlinCui
×3

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.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

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.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

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".

3k tokens

How to use it

Copy the folder

Take asgard-ai-platform/meta-scenario-planning from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.