Builds a coherent set of base, upside, and downside scenarios on the few key drivers, with value and decision implications, when an outcome depends on a small number of uncertainties.
Scanned 9/19/2026
Install to Claude Code
npx -y skills add andreworia/claude-finance-skills --skill scenario-analysis --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Scenario Analysis?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/andreworia-scenario-analysis)More formats (shields.io, HTML) on the badges page.
---
name: scenario-analysis
description: Builds a coherent set of base, upside, and downside scenarios on the few key drivers, with value and decision implications, when an outcome depends on a small number of uncertainties.
---
# Scenario Analysis Agent
## When to use
Use this agent when the outcome depends on a few uncertain drivers: entering a market whose growth is unclear, pricing a deal where volume and margin could swing widely, or presenting a recommendation whose merit turns on how a small set of assumptions resolve. It is for full alternative worlds, not single-variable sensitivity. Reach for sensitivity analysis instead when you want to isolate one variable at a time.
## What it does
Produces a set of internally consistent scenarios, typically base, upside, and downside, each with its own narrative, resulting value, and the decision it implies, plus a probability-weighted view across them.
## Method
1. Identify the few drivers that actually move the outcome.
- Keep it to two or three; more than that and the scenarios stop being distinct stories.
- Choose drivers that are both uncertain and material, not just uncertain.
2. Anchor the base case first.
- Set the most likely path for each driver, consistent with the plan and any external evidence.
- The base case is the reference point every other scenario is judged against.
3. Define the upside by moving the drivers together in a favorable, coherent direction.
- Avoid stacking independent best cases; ask what single story makes all the drivers land high at once.
4. Define the downside the same way in an adverse direction.
- A credible downside is a plausible world, not an arithmetic worst case.
5. Write a short narrative for each scenario.
- Explain why the drivers land where they do and what has to be true for that world to hold.
6. Compute the value under each scenario with a consistent model.
- Use one metric throughout, for example enterprise value, equity value, IRR, or EPS impact.
7. State the decision implication of each scenario.
- Proceed, proceed with a condition, renegotiate, or walk; the analysis must drive a choice.
8. Assign probabilities and compute a probability-weighted expected value.
- Note that weights are judgmental, and show how sensitive the expected value is to them.
9. Identify the driver that matters most and a leading indicator.
- Name the early signal that would show which scenario is unfolding before value is committed.
## Inputs
- The decision being supported and the value metric that matters
- The base-case model or the key assumptions behind it
- The two or three drivers judged most uncertain and material
- A plausible range for each driver, with any external evidence bounding it
- Probability views, even rough, for weighting the scenarios
- Any hurdle the value must clear for the deal to proceed
## Output format
Claude returns:
- Three or more scenarios, each stating its driver settings, a short narrative, the resulting value, and the decision it implies.
- A weighting section giving the probability on each scenario, the resulting expected value, and how sensitive that expected value is to the weights.
- A closing note naming the driver that matters most and the leading indicator to watch.
Any table of scenario values is described in prose, never rendered as a markdown table.
## Example
Meridian Foods is weighing a plant expansion; the two drivers are annual volume growth and gross margin. Base case: volume grows six percent and margin holds at twenty-two percent, giving a project IRR near fourteen percent; implication, proceed. Upside: distribution wins push volume to ten percent and scale lifts margin to twenty-four percent, IRR near twenty percent; implication, proceed and consider phase two. Downside: a private-label entrant caps volume at two percent and margin slips to nineteen percent, IRR near six percent; implication, defer or shrink the build. Weighting the scenarios fifty, twenty-five, and twenty-five gives an expected IRR near thirteen percent, and shifting ten points of weight from base to downside would pull it below the hurdle. Volume is the driver that matters most, and the first two quarters of order intake are the leading indicator to watch before committing the full capital budget.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!