pre-mortem

Identify failure causes using prospective hindsight for plans and projects.

3|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/dvy1987/agent-loom --skill pre-mortem-dvy1987
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-mortem
Source: https://github.com/dvy1987/agent-loom/tree/main/.agents/skills/pre-mortem
Command: npx skills add https://github.com/dvy1987/agent-loom --skill pre-mortem-dvy1987

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A structured method to surface realistic, specific failure causes before a major commitment so teams can prioritize risks and define concrete prevention actions rather than relying on overly optimistic forward planning.

Core Features & Use Cases

  • Prospective hindsight framing: Places stakeholders in a future-failure scenario to bypass optimism bias and elicit deeper root causes.
  • Divergent cause generation: Guides users through five distinct cause types (obvious, slow leak, wrong assumption, external surprise, people/organizational) to ensure breadth and depth.
  • Prioritization and remediation: Uses an informal impact × blindness ranking to prioritize causes and converts each top cause into ownerable prevention actions with deadlines.
  • Use Case: Run just before a major launch, roadmap commitment, or strategic decision to reduce the chance of costly, avoidable failure.

Quick Start

Run a pre-mortem for the upcoming project with a 6-month horizon, list ranked root causes, and provide concrete prevention actions with owners and deadlines.

Frequently Asked Questions about pre-mortem

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

FAQPage Schema
What is a pre-mortem and how does prospective hindsight help with project planning?▼

A pre-mortem uses prospective hindsight to place stakeholders in a future-failure scenario, bypassing optimism bias to elicit deeper root causes. It surfaces realistic, specific failure causes before a major commitment so teams can prioritize risks and define concrete prevention actions.

How do I run a pre-mortem to identify risks before a product launch?▼

To run a pre-mortem, set a failure scenario with a specific horizon, generate diverse failure causes across five categories, rank them by informal impact and blindness, then convert top causes into concrete prevention actions with assigned owners and deadlines.

When should I conduct a pre-mortem for strategic decisions or roadmap commitments?▼

Conduct a pre-mortem just before a major launch, roadmap commitment, or strategic decision. Running it before major commitments surfaces overlooked risks across product roadmaps, reducing the chance of costly, avoidable failure.

What types of failure causes should I identify during risk identification?▼

During risk identification, generate causes across five distinct types: obvious causes, slow leaks, wrong assumptions, external surprises, and people or organizational issues. This ensures breadth and depth in surfacing realistic failure scenarios.

How do I prioritize root causes and create prevention actions in project planning?▼

Prioritize root causes using an informal impact multiplied by blindness ranking to find the most critical risks. Convert each top-ranked cause into ownerable prevention actions with specific deadlines to ensure accountability.

Does pre-mortem risk identification work for avoiding optimism bias in forward planning?▼

Yes, pre-mortem risk identification specifically bypasses optimism bias by framing the project as already failed. This prospective hindsight approach elicits deeper root causes than standard forward planning, ensuring overlooked risks are surfaced.