Agent skill

scenario-planning

When the user wants to analyze supply chain scenarios, perform risk analysis, evaluate what-if scenarios, or build contingency plans. Also use when the user mentions "scenario analysis," "what-if planning," "risk scenarios," "contingency planning," "monte carlo simulation," "sensitivity analysis," "stress testing," or "disruption planning." For demand uncertainty, see demand-forecasting. For S&OP scenario integration, see sales-operations-planning.

majiayu000534★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill scenario-planning --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 40 KB
Bundled scripts: none
Path: skills/analysis/scenario-planning/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

You are an expert in supply chain scenario planning and risk analysis. Your goal is to help organizations evaluate alternative futures, assess risks, develop contingency plans, and make robust decisions under uncertainty.

How it works

  • Performs an initial assessment to gather planning context, business environment, scope, objectives, and data/resources.
  • Provides a Scenario Planning Framework with types of analysis: Sensitivity Analysis, What-If Scenarios, Monte Carlo Simulation, Strategic Scenarios, and Stress Testing.
  • Outlines a Scenario Development Process with Phase 1 Define Scope & Objectives, Phase 2 Identify Key Uncertainties (external and internal), Phase 3 Define Scenarios (Driver-Based, Event-Based, Monte Carlo), Phase 4 Model Scenarios (build base model, apply changes, simulate over time, compute metrics, compare scenarios).
  • Includes concrete modeling constructs and code snippets that illustrate state representation (SupplyChainState), scenario management (ScenarioModel), and basic evaluation/effects on inventory, service level, and costs.
  • Provides a Monte Carlo Simulation section describing probabilistic analysis, process steps, and a Python-based implementation outline for running simulations, generating demand, costs, supply reliability, and calculating outcomes like total_cost and service_level.

When to use it

Use when the user wants to analyze supply chain scenarios, perform risk analysis, evaluate what-if scenarios, or build contingency plans. Also apply when user mentions terms like "scenario analysis," "what-if planning," "risk scenarios," "contingency planning," "monte carlo simulation," "sensitivity analysis," "stress testing," or "disruption planning."

What it can touch

  • Tools: claude-code
  • Data structures: Python code blocks define dataclasses (SupplyChainState), and classes (ScenarioModel, MonteCarloScenarioAnalysis) used to model and analyze scenarios.
  • Operations include defining base state, adding scenarios, evaluating scenarios over time, and performing Monte Carlo simulations with distributions for demand, costs, and supply reliability.

Caveats

  • License: MIT
  • The skill includes example Python code snippets and may require adaptation to specific environments; ensure dependencies (numpy, pandas, matplotlib, scipy) are available.
  • No promises of specific outcomes; described methods are for modeling and comparison, not guaranteed results.
From the SKILL.md

# Scenario Planning You are an expert in supply chain scenario planning and risk analysis. Your goal is to help organizations evaluate alternative futures, assess risks, develop contingency plans, and make robust decisions under uncertainty. ## Initial Assessment Before building scenario plans, understand: 1. **Planning Context** - What decisions need to be made? - What uncertainties or risks are most concerning? - Planning horizon? (short-term tactical vs. long-term strategic) - Current planning process and tools? 2. **Business Environment** - Key market uncertainties? (demand, supply, pricing) - External risks? (geopolitical, natural disasters, economic) - Internal vulnerabilities? (single-source suppliers, capacity constraints) - Historical disruptions experienced? 3. **Scope & Objectives** - What part of supply chain? (end-to-end, specific segment) - Quantitative analysis or qualitative scenarios? - One-time analysis or ongoing process? - Decision context? (investment, strategy, operations) 4. **Data & Resources** - Historical variability data available? - Cost and performance data? - Risk databases or incident logs? - Modeling tools and capabilities? --- ## Scenario Planning F

What's inside
Steps it walks through
  1. Initial Assessment
  2. Scenario Planning Framework
  3. Types of Scenario Analysis
  4. Scenario Development Process
  5. Phase 1: Define Scope & Objectives
  6. Phase 2: Identify Key Uncertainties
  7. Phase 3: Define Scenarios
  8. Phase 4: Model Scenarios
  9. Monte Carlo Simulation
  10. Probabilistic Scenario Analysis
  11. Sensitivity Analysis
  12. One-Way Sensitivity
  13. Multi-Way Sensitivity (Tornado Diagram)
  14. Risk Assessment & Quantification
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the scenario-planning skill do?

When the user wants to analyze supply chain scenarios, perform risk analysis, evaluate what-if scenarios, or build contingency plans. Also use when the user mentions "scenario analysis," "what-if planning," "risk scenarios," "contingency planning," "monte carlo simulation," "sensitivity analysis," "stress testing," or "disruption planning." For demand uncertainty, see demand-forecasting. For S&OP scenario integration, see sales-operations-planning.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill scenario-planning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going