Pre-Mortem Risk Analysis FAQs

Question 1

When is the best time to use this skill?

Accepted Answer

It is most effective when preparing for a launch, during the final planning stages of a feature, or when you need to stress-test a product strategy to identify overlooked dependencies.

Question 2

Can this skill analyze external files like PRDs?

Accepted Answer

Yes, if you provide a PRD or product plan file, the skill will read it thoroughly to understand the product, target market, and key assumptions before starting the analysis.

Question 3

What output does the pre-mortem skill provide?

Accepted Answer

It generates a structured markdown document named 'PreMortem-[product-name]-[date].md' containing the risk analysis, categorization, and specific action plans for launch-blocking issues.

Question 4

How does the skill distinguish between different types of risks?

Accepted Answer

It uses three categories: Tigers (real problems requiring action), Paper Tigers (valid-looking but overblown concerns), and Elephants (unspoken worries that the team isn't discussing enough).

Question 5

What is the purpose of a pre-mortem analysis?

Accepted Answer

A pre-mortem is an exercise where a team imagines a project has failed and works backward to determine what caused that failure, allowing them to prevent those issues in the real world.

Pre-Mortem Risk Analysis

Key Features

Use Cases

Pre-Mortem Risk Analysis

Key Features

Use Cases