pre-mortem

Categorize launch risks as Tigers, Paper Tigers, and Elephants with owners and due dates.

2|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/skytiger6724/qwen-skills --skill pre-mortem-skytiger6724
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-mortem
Source: https://github.com/skytiger6724/qwen-skills/tree/main/pre-mortem
Command: npx skills add https://github.com/skytiger6724/qwen-skills --skill pre-mortem-skytiger6724

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It keeps launch teams from rediscovering risks later by forcing a disciplined pre-mortem that surfaces real Tigers, Paper Tigers, and Elephants before the release window closes.

Core Features & Use Cases

  • Structured Failure Imagination: Envision a post-launch failure scenario in 14 days to uncover what went wrong, what was missed, and what assumptions were flawed.
  • Risk Categorization: Separate concerns into Tigers (urgent threats), Paper Tigers (likely overblown worries), and Elephants (quiet yet risky assumptions), and note their urgency level.
  • Action Plan Documentation: For each launch-blocking Tiger, record the risk, mitigation action, owner, and due date with cross-functional accountability, ideal for PRD reviews or go-to-market stress tests.

Quick Start

Run the pre-mortem skill on the product requirements document to identify Tigers, Paper Tigers, and Elephants.

Frequently Asked Questions about pre-mortem

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

FAQPage Schema
How do I conduct a pre-mortem analysis for a product launch?

To conduct a pre-mortem analysis, envision a post-launch failure scenario within 14 days to uncover what went wrong, then categorize risks into Tigers, Paper Tigers, and Elephants with assigned urgency levels.

What is the difference between Tigers, Paper Tigers, and Elephants in risk analysis?

In risk analysis, Tigers are urgent threats requiring action, Paper Tigers are likely overblown worries, and Elephants are quiet yet risky assumptions that need documentation before a product release.

How do I document launch-blocking risks for a PRD review?

Document launch-blocking risks by recording the specific threat, mitigation action, owner, and due date with cross-functional accountability to ensure readiness during PRD reviews.

When do I need to classify launch readiness risks before a release?

You need to classify launch readiness risks before a release when conducting go-to-market stress tests or PRD reviews that require documented risk classification and assigned urgency.

Does pre-mortem analysis work for cross-functional product strategy alignment?

Pre-mortem analysis works for cross-functional product strategy alignment by forcing teams to surface real threats and flawed assumptions collaboratively before the release window closes.

What is the best way to stress-test product launch readiness?

The best way to stress-test product launch readiness is to imagine product progress halted, log the categorized risks, and create launch-blocking action plans with owners and due dates.