Pre-Mortem Plan Analysis
Pre-mortem plan analysis. Imagine the plan failed 12 months from now and work backwards to find the weaknesses. Surfaces assumptions, dependencies, and execution risks before committing resources. Produces a structured Challenge Report that maps vulnerabilities and suggests hardening actions.
✨ What it does
- Extracts core assumptions from the plan
- Rates each assumption by confidence and impact
- Maps vulnerabilities where low confidence meets high impact
- Identifies dependency chains and weakest links
- Assesses reversibility of bets and commitments
- Generates kill switches and hardening actions
🎯 When to use it
- Before committing significant resources to a plan
- Before presenting to the board or investors
- When feedback has been one-sidedly positive
- When there is pressure to move fast and figure it out later
🚀 How to use
Trigger: /em:challenge
Trigger with the slash command /em:challenge <plan> or by asking to run a pre-mortem on a plan. Provide the plan details in the request. The skill will analyze the plan and produce a Challenge Report.
Example prompts:
/em:challenge Our Q3 product roadmap
Run a pre-mortem on this go-to-market plan: [paste plan]
📄 Output: A Challenge Report with core assumptions, vulnerability map, dependency chain, reversibility assessment, kill switches, and hardening actions.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/c-level-advisor/executive-mentor/skills/challenge .claude/skills/challengeSkill source: c-level-advisor/executive-mentor/skills/challenge/SKILL.md
⚠️ Good to know
The skill requires a plan to analyze and does not validate the plan's underlying data; it relies on the information provided.
❓ FAQ
What is the purpose of the pre-mortem analysis?
It helps find weaknesses in a plan before reality does, by imagining the plan failed and working backwards to identify assumptions and risks.
What are the key outputs of the challenge?
The output is a Challenge Report that includes core assumptions, a vulnerability map, dependency chain, reversibility assessment, kill switches, and hardening actions.
How are assumptions rated?
Assumptions are rated on confidence (High, Medium, Low, Unknown) and impact if wrong (Critical, High, Medium, Low).
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.