Menu
Free Claude Skill

Check your plan before you do, not after

A pre-mortem analysis based on Gary Klein and Kahneman. The AI places you into a future where your plan has failed and reconstructs with you why. 30 percent more failure points found than with normal risk analysis.

Based on research by Gary Klein, 1985
Daniel Kahneman signed document
Specifically in 30 minutes
7Failure categories
15+Modifications planned
30 minutesLead time
Pre-mortem report
SaaS launch in 30 days, 500 prospects
High
Onboarding friction (chances 4, impact 5)
Signup to activation under 40%
Kans x Impact
Kill criteria

Why pre-mortem Works

Standard risk analysis activates your optimism filter. A pre-mortem bypasses that filter by placing your thoughts in the future. You find more, you find concrete details, you intervene sooner.

30 percent more failure modes

Klein (1985) found that teams using a pre-mortem identified significantly more risks than teams using standard analyses.

Counteracting overconfidence bias

Kahneman wrote that this is the only technique that combats overconfidence and can be implemented in 30 minutes.

Concrete, not abstract

No vague “competitor might do something.” Specific failure modes with probability, impact, and early warning signs that you can monitor.

Ready in 30 minutes

Short structure, no workshop needed. Ideal for solo entrepreneurs, launches or decisions with a short turnaround time.

This is how it works pre-mortem

You share your plan, the AI takes you to a future where it has flopped and works back with you. Eight steps, each with a clear goal and output.

What you get back

A list of 15+ failure modesConcrete per plan, not generic. Per failure mode a category, probability, impact and risk score.
Top 5 critical risksSorted by chance x impact. These are the risks you should prioritise addressing or accepting.
Early warning signs per riskObservable metrics and thresholds. Without signals, you cannot intervene in time.
Prevention and mitigationTwo options per risk: prevent it or limit the damage if it does happen.
Kill criteriaThe points at which you stop the plan. Prevents the sunk cost fallacy if things go wrong.
Honest go-no-go adviceContinue, adjust or stop. Based on the risk profile, not on your enthusiasm.
1

Map out the plan

Decision, timeline, resources, success and failure definition, stakeholders. Vague is not enough.

2

Time travel

It's six months later and your plan has catastrophically failed. Concrete consequence.

3

15+ functioning modes

From seven categories: execution, assumption, external, communication, timing, scope, people.

4

Kans x impact scores

Rate each failure mode from 1 to 5 on probability and impact. Sort by risk score. Extract top 5.

5

Early warning signs

For critical risk, a metric, a threshold, and an intervention point.

6

Prevention or mitigation

What are you changing now, what's your plan if it does happen?.

7

Kill criteria

The points at which you stop. Decide this IN ADVANCE, before sunk cost traps you.

8

Go-no-go report

Brief summary with plan, risks, signals, adjustments, kill criteria, final assessment.

Example output

A pre-mortem on a fictional SaaS launch. Not all rows visible, but this is what the output looks like.

Pre-mortem: SaaS launch in 30 days

Top 5 of 17 failure modes
Operating modeCategoryThanksImpactScore
Onboarding friction reduces activation below 40 percentPerformance4520
The price is higher than the willingness to pay for early adoptersAssumption3515
Founder burns out before public launchMen's3412
Concurrent X launches similar feature in Q3Extern2510
LinkedIn audience is not clicking through on launch postCommunication428

Without vs pre-mortem meeting

You're doing the same launch. Once without, once with a pre-mortem beforehand. The difference lies in what you anticipated in advance.

Without pre-mortem

  • Your launch goes live, activation is 22 percent but you only discover it after two weeks.
  • You didn't agree on a threshold, so you're hesitating between “waiting” or “pivoting”.
  • You've already spent €3,000 on ads. Sunk cost is keeping you committed to the plan.
  • Looking back, you say: I should have seen this coming. But in hindsight, every mistake in judgment is clear.
  • Your kill criteria are set in panic, not from rationality.

Pre-mortem meeting

  • You know in advance that activation below 40 percent is a red flag.
  • On day 3, you’ll see activation is at 28 percent. You’ll intervene immediately with an onboarding fix.
  • You know in advance: at 20 percent activation in week two, you stop the ads. No question.
  • You don't roll into sunk costs. The kill criteria were fixed when you were still rational.
  • You see three risks you would never have thought of alone. Time travel did the work.

The Prompt structure behind

The skill is built around a strict system prompt. You don't need to write a prompt yourself, but this way you'll know what's happening under the hood.

SKILL.md
# Role You are a pre-mortem analyst. You protect the user from their own optimism. # Steps 1. Map out the plan — decision, timeline, resources, success, failure, stakeholders. Time travel “It's six months later, the plan has failed catastrophically” 3. Here are at least 15 failure modes: 1. **Overheating:** Components exceed their safe operating temperature, leading to malfunction or permanent damage. 2. **Underperformance:** The system or component does not achieve its expected output or efficiency. 3. **Complete Shutdown:** The system or component ceases to operate entirely. 4. **Intermittent Operation:** The system or component functions erratically, turning on and off unexpectedly. 5. **Data Corruption:** Information stored or transmitted becomes inaccurate or unreadable. 6. **Mechanical Jamming:** Moving parts become stuck or obstructed, preventing operation. 7. **Electrical Short Circuit:** An unintended low-resistance path allows excess current to flow, potentially causing damage. 8. **Loss of Connectivity:** The system or component fails to establish or maintain communication with other devices or networks. 9. **Software Crash:** A program or operating system unexpectedly terminates. 10. **Physical Damage:** Components are broken, cracked, or deformed due to external forces. 11. **Corrosion:** Material degradation due to chemical or electrochemical reactions. 12. **Wear and Tear:** Gradual deterioration of components due to normal usage over time. 13. **Leakage:** Fluids or gases escape from their intended containment. 14. **Power Failure:** Loss of electrical power supply causes the system to stop. 15. **Incorrect Input Processing:** The system fails to interpret or act upon input data as intended. 16. **Environmental Exposure:** Damage caused by exposure to elements like moisture, dust, extreme temperatures, or radiation. 17. **Human Error:** Incorrect operation, maintenance, or installation by a user. 18. **Component Fatigue:** Material failure due to repeated stress cycles. out of 7 categories 4. Score On chance (1-5) and impact (1-5), sort by risk score. Early warning signs for criticism failure point with threshold 6. Prevention + mitigation per la quantità di rischio 7. Kill criteria predefine 8. Go-no-go report with fair judgement # Cartoon Cold, concrete, Dutch. No pep talk. Role is to protect, not motivate.

Frequently Asked questions

Frequently asked questions about the pre-mortem skill and how to use it in Claude.

Wat is een pre-mortem precies?

A pre-mortem is the reverse of a post-mortem. You do it BEFORE the launch or decision, not after. You imagine that your plan has failed and write back what happened. Gary Klein showed in his research that teams using this method found thirty percent more failure points than teams that did standard risk analyses.

What is this skill suitable for

For every decision with real consequences: a product launch, a hire that's not easily reversed, a pivot, a large expenditure, a market entry, an investment. Not for small daily choices, as the overhead would be too great.

How long does a session last

For a thoughtful pre-mortem on an important decision, allow thirty to sixty minutes. Kahneman specifically cited this as the reason the technique works in practice. You can do it faster if necessary, but then you lose nuance.

Why not just do a risk analysis

A standard risk analysis activates your optimism filter. You look for risks from a position where you still believe in the plan. The pre-mortem shifts you to a future where you no longer believe in the plan, because it has failed in that future. That small difference leads to a completely different thought process.

Does the skill provide go-no-go advice

Yes, as the final step. It is a fair judgement based on the risk profile that you have built together. Not as a rigid rule, but as a concrete signal. The final decision remains yours.

How do I install the skill in Claude

Download the zip, extract it, and upload SKILL.md into Claude via a skill or project. You can also directly use the content as a system prompt within a project. The skill works in Claude Pro, Team, and Enterprise.

Free download

Download de pre-mortem skill

A zip with SKILL.md. Upload in Claude via a skill or project. Works in Pro, Team, and Enterprise. No account needed, no payment, no fuss.

SKILL.md included Dutch Ready to use

Sea Discover skills

The pre-mortem is one of the skills we're building for entrepreneurs. Check out the rest or read how AI is changing your workflow.