pre-mortem

Stress-test plans by imagining failure and classifying risks into Tigers, Paper Tigers, and Elephants.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/MilUX-Ltd/footing --skill pre-mortem-milux-ltd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-mortem
Source: https://github.com/MilUX-Ltd/footing/tree/main/footing/template/Skills/pm-skills/pre-mortem
Command: npx skills add https://github.com/MilUX-Ltd/footing --skill pre-mortem-milux-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams commit to plans, bids, and launches while carrying unspoken doubts and unexamined risks that only surface after failure. This Skill runs a structured pre-mortem that assumes the plan has already failed and works backward to expose the real risks while there is still time to act. ## Core Features & Use Cases - Failure Simulation: Imagines the plan failing after launch and traces back what went wrong, what was missed, and where the team was overconfident. - Risk Classification: Sorts risks into Tigers (real, evidence-backed), Paper Tigers (overblown concerns to document, not fund), and Elephants (unspoken worries needing investigation). - Action Planning: Classifies each Tiger as blocking, fast-follow, or track, then writes mitigation plans with owners and dates for every blocking risk. - Use Case: Two weeks before submitting a major bid, run a pre-mortem to surface the delivery risk nobody has raised, classify it as blocking, and assign a mitigation owner before the submission deadline. ## Quick Start Run a pre-mortem on the attached launch plan and list the blocking Tigers with mitigation owners and dates.

Frequently Asked Questions about pre-mortem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a pre-mortem on a project plan?▼

Read the plan to understand its objective, assumptions, and timeline, then imagine it has failed and work backward to identify what went wrong. Sort the findings into Tigers, Paper Tigers, and Elephants, then write mitigation plans for the blocking risks.

What is the difference between a pre-mortem and a red team review?▼

A red team attacks the plan's load-bearing assumptions as they stand now, while a pre-mortem assumes the plan has already failed and surfaces what the team is not saying. This Skill is the forward complement to strategy-red-team and works best near a commit point.

When should I use a pre-mortem instead of a standard risk register?▼

Use a pre-mortem near a commit point such as a bid submission, launch, or rollout, when you need to catch hidden worries while there is still time to act. It is designed to surface unspoken concerns that standard risk tracking often misses.

What are Tigers, Paper Tigers, and Elephants in risk analysis?▼

Tigers are real, evidence-backed risks needing action. Paper Tigers are overblown concerns to document for stakeholder alignment without spending resources. Elephants are unspoken worries nobody is validating that should be investigated before committing.

What are the limitations of a pre-mortem exercise?▼

A pre-mortem depends on honest input and cross-functional perspectives; a commercial-only view can miss operational risks. It also requires follow-up, so revisit the findings two to three weeks before the commit date to confirm mitigations are on track.