forecast-premortem

forecast-premortem is a skill for Claude Code, Codex from nicepkg/ai-workflow. It costs 76 tokens per session (3,936 once invoked), scanned A, original, MIT.

A risk-checking technique that assumes a prediction or plan has already failed and then works backward to ask why. This is called a premortem, and it is used to uncover risks before they happen.

In plain words
What is it for?
Use it to stress-test predictions, plans, deadlines, and other important decisions where hidden risks could matter.
Why use it?
It challenges overconfidence and turns vague concerns into specific possible failure causes. This helps teams spot blind spots and make forecasts more realistic.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/nicepkg/ai-workflow/forecast-premortem
Any agent
npx skills add nicepkg/ai-workflow --skill forecast-premortem
Clone the repo
git clone --depth 1 https://github.com/nicepkg/ai-workflow

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 forecast-premortem

README.md
[![agentmods](https://agentmods.dev/badge/skills/nicepkg/ai-workflow/forecast-premortem.svg)](https://agentmods.dev/skills/nicepkg/ai-workflow/forecast-premortem)
Your own site
<a href="https://agentmods.dev/skills/nicepkg/ai-workflow/forecast-premortem"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/forecast-premortem.svg" alt="Measured on agentmods" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,936 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00076 $0.03936
Opus 5 $0.00038 $0.01968
Sonnet 5 $0.00015 $0.00787
Haiku 4.5 $0.00008 $0.00394

Measured yesterday against content hash 3d534a696fe7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

forecast-premortem 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 yesterday.

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.

workflows/product-manager-workflow/.claude/skills/forecast-premortem/SKILL.md · 463 lines

How it starts

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

Forecast Pre-Mortem

Table of Contents


What is a Forecast Pre-Mortem?

A forecast pre-mortem is a stress-testing technique where you assume your prediction has already failed and work backward to construct the history of how it failed. This reveals blind spots, tail risks, and overconfidence.

Core Principle: Invert the problem. Don't ask "Will this succeed?" Ask "It has failed - why?"

Why It Matters:

  • Defeats overconfidence by forcing you to imagine failure
  • Identifies specific failure modes you hadn't considered
  • Transforms vague doubt into concrete risk variables
  • Widens confidence intervals appropriately
  • Surfaces "unknown unknowns"

Origin: Gary Klein's "premortem" technique, adapted for probabilistic forecasting


When to Use This Skill

Use this skill when:

  • High confidence (>80% or <20%) - Most likely to be overconfident
  • Feeling certain - Certainty is a red flag in forecasting
  • Prediction is important - Stakes are high, need robustness
  • After inside view analysis - Used specific details, might have missed big picture
  • Before finalizing forecast - Last check before committing

Do NOT use when:

  • Confidence already low (~50%) - You're already uncertain
  • Trivial low-stakes prediction - Not worth the time
  • Pure base rate forecasting - Premortem is for inside view adjustments

Interactive Menu

What would you like to do?

Core Workflows

1. Run a Failure Premortem - Assume prediction failed, explain why 2. Run a Success Premortem - For pessimistic predictions (<20%) 3. Dragonfly Eye Perspective - View failure through multiple lenses 4. Identify Tail Risks - Find black swans and unknown unknowns 5. Adjust Confidence Intervals - Quantify the adjustment 6. Learn the Framework - Deep dive into methodology 7. Exit - Return to main forecasting workflow

Read the full file on GitHub · 463 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. yesterday First seen · 463 lines · 76 tokens per session scan A 3d534a696fe7

Subscribe to this mod's changes

forecast-premortem is a skill published in the GitHub repository nicepkg/ai-workflow (283 stars, last pushed 7mo ago), licensed MIT. It adds 76 tokens to every session and 3,936 once invoked, about $0.0004 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-09-03.

Related

Other skills, from other repositories

stale-sweep

Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…

googleapis/mcp-toolbox · 159 tokens

github-issue-triage

Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep…

zeroclaw-labs/zeroclaw · 140 tokens

triage

Triage open herdr GitHub issues into a concise decision-first Markdown table. Use when the user says "triage", asks to triage open issues, asks which issues need attention, or wants issue priority/recommendation lights for herdr.

herdrdev/herdr · 53 tokens

backlog-technical-project-manager

Technical project management for Backlog.md workstreams using coordinated sub-agents. Use only when the user explicitly asks Codex to take over one or more existing Backlog.md tasks (for example: "act as TPM", "coordinate these tasks", "delegate to sub-agents"). Orchestrate planning, implementation, and finalization…

MrLesk/Backlog.md · 90 tokens

things-mac

Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.

elizaOS/eliza · 67 tokens

devloop

Goal-driven development loop — define objective, write rules with key-results, verify visually, sync to issue tracker.

x-cmd/x-cmd · 25 tokens