aped-pre-mortem

Generate ranked failure scenarios and mitigations from PRD, architecture, and epics artefacts.

2|Updated Mar 12, 2026

Search Tags:#epics #product planning #failure modes #risk analysis #pre-mortem #mitigation planning

Ready to run

npx skills add https://github.com/yabafre/aped-claude --skill aped-pre-mortem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aped-pre-mortem
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-pre-mortem
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-pre-mortem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams avoid building on risky assumptions by forcing a structured review of how the project could plausibly fail before implementation begins.

Core Features & Use Cases

Failure-scenario setup: Reads the current PRD, architecture, and epics artefacts to anchor the pre-mortem in the actual plan.
Independent risk brainstorming: Generates specific failure scenarios across technical, scope, integration, process, and user risk categories.
Risk ranking and mitigation: Scores likelihood × impact, produces a mitigation table for the highest-priority risks, and writes a pre-mortem report for downstream use.

Quick Start

Use aped-pre-mortem when you want to turn a “we should be fine” plan into a ranked, mitigated list of what could go wrong before implementation starts.

Frequently Asked Questions about aped-pre-mortem

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

FAQPage Schema

How do I run a pre-mortem risk analysis before implementation begins?▼

Pre-mortem risk analysis prevents late-stage surprises by generating ranked failure scenarios before implementation. It reads existing PRD, architecture, and epics artefacts to anchor the review, then scores likelihood and impact across technical, scope, integration, process, and user risk categories.

When do I need pre-mortem analysis in product planning?▼

Pre-mortem analysis is needed during the PRD, architecture, and epics stage of product planning. It forces a structured review of how a project could plausibly fail before implementation starts, turning risky assumptions into a ranked, mitigated list of failure scenarios.

What's the best way to identify failure modes in epics planning?▼

The best way to identify failure modes in epics planning is independent risk brainstorming across technical, scope, integration, process, and user risk categories. Scoring likelihood by impact produces a mitigation table for highest-priority risks and writes a pre-mortem report for downstream use.

Can I use pre-mortem mitigation planning with existing PRD and architecture documents?▼

Yes, pre-mortem mitigation planning reads your current PRD, architecture, and epics artefacts to anchor the analysis in the actual plan. It produces a mitigation table for the highest-priority risks and feeds downstream epics and verification checks.

Does pre-mortem risk ranking cover integration and process risks?▼

Yes, pre-mortem risk ranking covers integration and process risks, along with technical, scope, and user risk categories. It scores likelihood and impact for each generated failure scenario, produces mitigations, and documents acceptance of residual risks in a downstream pre-mortem report.

What limitations does a pre-mortem approach have for risk analysis?▼

A pre-mortem approach for risk analysis is limited to the planning stage and depends on existing PRD, architecture, and epics artefacts. It generates hypothetical failure scenarios and mitigations but cannot predict every issue, meaning some residual risks must be formally accepted.