pre-mortem

Analyzes PRDs and launch plans to classify risks as Tigers, Paper Tigers, or Elephants.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill pre-mortem-choi-keith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-mortem
Source: https://github.com/Choi-Keith/skill-arsenal-ultra/tree/main/plugins/pm-skills/pm-execution/skills/pre-mortem
Command: npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill pre-mortem-choi-keith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often discover critical product risks only after launch, when it is too late to act. This Skill runs a structured pre-mortem analysis on a PRD or launch plan, surfacing real threats, overblown concerns, and unspoken worries before release. ## Core Features & Use Cases - Three-Way Risk Classification: Categorizes every potential failure point as a Tiger (real risk), Paper Tiger (exaggerated concern), or Elephant (undiscussed worry). - Urgency Triage: Grades real risks as launch-blocking, fast-follow (within 30 days), or track-and-monitor items. - Action Planning: Produces mitigation plans with owners and due dates for every launch-blocking risk, saved as a markdown document. - Use Case: Two weeks before a major feature launch, paste your PRD and receive a structured risk report distinguishing genuine blockers from stakeholder anxieties, with concrete mitigation actions. ## Quick Start Run a pre-mortem analysis on my PRD for the upcoming checkout redesign launch and list the launch-blocking risks with mitigation plans.

Frequently Asked Questions about pre-mortem

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

FAQPage Schema
How do I run a pre-mortem analysis on a product launch plan?

Provide your PRD or launch plan and the analysis imagines the product failing 14 days after launch, then works backward to identify causes. Each risk is classified and graded, with action plans created for launch-blocking issues.

What is the difference between a Tiger, Paper Tiger, and Elephant risk?

A Tiger is a real, evidence-based risk requiring action. A Paper Tiger is an exaggerated concern not worth heavy resources. An Elephant is an unspoken worry or unvalidated assumption that needs investigation before launch.

When should a product team run a pre-mortem?

Run it during launch preparation, ideally 2-3 weeks before release, and repeat it before launch to verify mitigations are in place. It also works for stress-testing product plans at any planning stage.

What output does a pre-mortem risk analysis produce?

It produces a structured markdown report saved as PreMortem-[product-name]-[date].md, containing classified risk lists and action plans for launch-blocking Tigers with risk description, mitigation, owner, and due date.

What are the limitations of a pre-mortem analysis?

The analysis quality depends on the completeness of the provided PRD and available market context. It identifies and prioritizes risks but does not execute mitigations, so teams must assign owners and track follow-through separately.