Pre-Mortem Risk Analysis FAQs

Question 1

What is a pre-mortem in software development?

Accepted Answer

A pre-mortem is a management technique where a team imagines a project has failed and works backward to determine what led to that failure, allowing them to strengthen the plan before work begins.

Question 2

How does it handle different risk severities?

Accepted Answer

The skill categorizes risks by severity; High-severity risks are considered blocking and require the user to either explicitly accept them or add a mitigation to the plan before proceeding.

Question 3

How does the Pre-Mortem skill avoid false positives?

Accepted Answer

The skill uses a mandatory verification checklist that requires the AI to read surrounding context (±20 lines), check for existing fallbacks, and verify scope before any risk is flagged as a 'Tiger'.

Question 4

Can I use this for quick code reviews?

Accepted Answer

Yes, the skill includes a 'quick' mode specifically optimized for Pull Requests and localized changes, providing a focused analysis in just 2-3 minutes.

Question 5

Does it provide solutions for the risks it identifies?

Accepted Answer

Yes, it features a 'Research mitigation options' workflow that scans your existing codebase for similar patterns and researches external best practices to suggest concrete fixes.

Pre-Mortem Risk Analysis

Key Features

Use Cases

Pre-Mortem Risk Analysis

Key Features

Use Cases