pre-mortem

Categorize launch risks into Tigers, Paper Tigers, and Elephants with owners and deadlines.

142|16|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/amplitude/builder-skills --skill pre-mortem-amplitude
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-mortem
Source: https://github.com/amplitude/builder-skills/tree/main/product-skills/skills/pre-mortem
Command: npx skills add https://github.com/amplitude/builder-skills --skill pre-mortem-amplitude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and surface potential launch risks by imagining a failed launch and working backward to find what went wrong, enabling proactive mitigation.

Core Features & Use Cases

  • Categorizes risks into Tigers (launch-blocking), Paper Tigers (not as scary as they seem), and Elephants (unspoken issues), with owners and deadlines.
  • Produces a structured risk register suitable for product, engineering, and PM teams before go-live.
  • Supports scenario planning for specs, launches, and feature rollouts to improve readiness.

Quick Start

Run a pre-mortem analysis on the upcoming launch by listing risks in Tigers, Paper Tigers, and Elephants and assigning 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 analysis for product launch readiness?▼

Run a pre-mortem by imagining a failed product launch, then working backward to categorize surfaced issues into Tigers, Paper Tigers, and Elephants. Assign specific owners and deadlines to each risk to build a structured mitigation plan.

How do I categorize launch risks using the Tiger and Elephant framework?▼

Categorize launch risks by severity: Tigers are launch-blocking issues, Paper Tigers are perceived risks that are less severe than expected, and Elephants are unspoken team concerns. This framework clarifies mitigation priorities for product and engineering teams.

When do I need to run a pre-mortem risk assessment for a feature rollout?▼

Run a pre-mortem risk assessment before any product launch or feature rollout to ensure launch readiness. It is required when you need to proactively identify potential failures, build a risk register, and establish mitigation plans with assigned owners.

Can I use pre-mortem risk categorization for cross-functional product teams?▼

Yes, pre-mortem risk categorization is designed for cross-functional product, engineering, and PM teams. It surfaces unspoken Elephants and launch-blocking Tigers across teams, producing a structured risk register suitable for collaborative go-live planning.

What do I need to create a structured launch risk register?▼

To create a structured launch risk register, you need clear risk criteria to categorize issues into Tigers, Paper Tigers, and Elephants, plus assigned owners and deadlines for each identified risk to ensure actionable mitigation planning.