scenario-planning SKILL.md skillA
scenario-planning from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/scenario-planning@git:20260829.2464776Pins git:20260829.2464776 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/corporate-strategy/skills/scenario-planning/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260829.2464776, committed Aug 29, 2026
- First version recorded
- Aug 29, 2026
- Size
- 3,402 bytes
- Repository stars
- 2,543
- License
- MIT
Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold, before a large irreversible commitment, or when a market, regulatory, or technology shift could invalidate the strategy.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Scenario planning Forecasting produces one number and false confidence. Scenario planning produces a plan that survives being wrong, which is the realistic goal. ## Separate what you know from what you are assuming List the plan's assumptions explicitly, then sort them: - **Predetermined** — things that will happen regardless. Demographics, contracted commitments, technology already deployed. Plan around them; do not spend analysis on them. - **Genuinely uncertain and load-bearing** — the plan changes materially depending on how they resolve. Almost every plan has **two or three** load-bearing uncertainties. Finding them is most of the value, and the exercise usually surfaces one nobody had articulated. ## Build scenarios from the uncertainties, not from moods The common failure is three scenarios named optimistic, base, and pessimistic — which is one scenario with the numbers scaled, and it teaches nothing. Take the two most consequential uncertainties and build the quadrants. Each scenario should be internally coherent: if demand is high *and* supply is constrained, what else follows — pricing, competitor behavior, regulatory attention? …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/scenario-planning@sha256:45b5fec715bf185cThe line at the top of this page pins the label git:20260829.2464776, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_r2i7ftvv2uffohgt)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Aug 29, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260829.2464776 latest | 2026-08-29 | 2464776 | 3,402 B | A | view · diff |
| git:20260829.635d8e8 | 2026-08-29 | 635d8e8 | 3,403 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3402 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_r2i7ftvv2uffohgt GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/scenario-planning GET https://markdownregistry.com/api/v1/blob/45b5fec715bf185c0f1ec18f8c879442013e99677e986d5701f2055cb0abc0c8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.