scenario-planning

scenario-planning is a skill for Claude Code, Codex from fzfclee/consulting-skills. It costs 46 tokens per session (752 once invoked), scanned A, original, Apache-2.0.

A structured method for planning decisions when important external conditions are uncertain. It builds several plausible futures instead of treating one forecast as certain.

In plain words
What is it for?
Use it to frame a strategic question, identify major uncertainties and trends, create scenarios, watch for warning signs, and plan robust or conditional actions.
Why use it?
It helps teams prepare for different outcomes and separate actions that make sense in every future from choices that depend on what happens.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to frame a strategic question, identify major uncertainties and trends, create scenarios, watch for warning signs, and plan robust or conditional actions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fzfclee/consulting-skills/scenario-planning
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add fzfclee/consulting-skills --skill scenario-planning
Clone the repo
git clone --depth 1 https://github.com/fzfclee/consulting-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for scenario-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/fzfclee/consulting-skills/scenario-planning/github.svg)](https://agentmods.dev/skills/fzfclee/consulting-skills/scenario-planning)
Your own site
<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/scenario-planning"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/scenario-planning/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for scenario-planning

Your own site · 80×15
<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/scenario-planning"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/scenario-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 752 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.00752
Opus 5 $0.00023 $0.00376
Sonnet 5 $0.00009 $0.00150
Haiku 4.5 $0.00005 $0.00075

Measured 12d ago against content hash 4a363d859d3e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

scenario-planning scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/scenario-planning/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scenario Planning

Use this skill to run Scenario Planning as a practical consulting method, not as a generic framework explanation.

Method Notes

  • Use critical uncertainties and signposts, not predictions.
  • Separate no-regret actions from contingent options.

Required Inputs

Collect or infer these inputs before execution:

  • strategic question
  • time horizon
  • critical uncertainties
  • known trends

If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.

When Not To Use

Do not use for a short-term forecast when one outcome can be estimated reliably. Scenarios explore a small set of high-impact uncertainties; they are not predictions or collections of generic risks.

Adjacent Methods

  • critical-uncertainties: identify the variables before building scenarios.
  • pre-mortem: rehearse failure of one chosen plan.
  • risk-matrix: prioritize known risk events.

Step-by-Step Execution

Step Required input How to execute Output
Frame decision and horizon Strategic question, time horizon, geography/market. State what decision must stay robust across futures. Scenario scope.
Identify uncertainties External trends, macro forces, market shifts. Separate relatively certain trends from high-impact uncertainties. Uncertainty list.
Build scenarios Top uncertainties and trends. Create 2-4 plausible scenarios with names and narratives. Scenario set.
Derive implications Scenario set and business model/strategy. Assess risks, opportunities, and constraints in each scenario. Scenario implications.
Choose options and signposts Implications. Define no-regret moves, contingent bets, and early indicators. Scenario action plan.

Output Template

### 1. Decision And Horizon
Focal decision:
Time horizon:
Geography / market:
Predetermined elements:

### 2. Critical Uncertainties
| Uncertainty | Range | Impact | Evidence | Signpost |
|---|---|---|---|---|
|  |  |  |  |  |

### 3. Scenarios
| Scenario | Coherent conditions | Implication | Vulnerable assumption |
|---|---|---|---|
|  |  |  |  |

### 4. Robust Moves And Signposts
| Move | Robust / contingent | Trigger | Owner |
|---|---|---|---|
|  |  |  |  |

### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:

Read the full file on GitHub · 87 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 87 lines · 46 tokens per session scan A 4a363d859d3e

Subscribe to this mod's changes

scenario-planning is a skill published in the GitHub repository fzfclee/consulting-skills (4 stars, last pushed 23d ago), licensed Apache-2.0. It adds 46 tokens to every session and 752 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.