pm-premortem

Run a pre-mortem on PMContext to classify launch risks and validate assumptions.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Wcof/PMSkill --skill pm-premortem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-premortem
Source: https://github.com/Wcof/PMSkill/tree/main/skills/delivery/pm-premortem
Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-premortem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams uncover the real reasons a launch could fail before release, so they can prioritize meaningful risk mitigation instead of reacting too late. It turns vague concern into a structured pre-mortem based on PMContext, with explicit risk classification, ownership, and next actions.

Core Features & Use Cases

  • Failure-backward risk analysis: Assumes the product failed 14 days after launch, then works backward with root-cause thinking to identify likely failure paths.
  • Structured risk triage: Classifies issues into Tiger, Paper Tiger, and Elephant categories, then ranks urgency as Launch-Blocking, Fast-Follow, or Track.
  • Assumption stress testing: Cross-checks low-confidence assumptions in PMContext and escalates fragile ones into actionable launch risks.
  • Red-team validation: Extracts load-bearing assumptions, defines falsifiable failure conditions, and proposes the cheapest test that can run this week.
  • Use cases: Ideal for launch readiness reviews, release risk workshops, stakeholder alignment before go-live, and stress-testing a PRD or PMContext before committing engineering effort.

Quick Start

Ask the AI to run pm-premortem on your PMContext when you want a launch-focused risk review with Tigers, action plans, and assumption checks.

Frequently Asked Questions about pm-premortem

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

FAQPage Schema
What is a premortem analysis for product launch readiness?

A premortem analysis for product launch readiness assumes a launch failed 14 days post-release, then works backward through root-cause thinking to identify likely failure paths before they occur.

How do I stress test PRD assumptions before committing engineering effort?

Stress test PRD assumptions by cross-checking low-confidence PMContext entries, extracting load-bearing assumptions, defining falsifiable failure conditions, and proposing the cheapest validation test to run this week.

How do I prioritize launch risks identified during release planning?

Prioritize launch risks by classifying issues into Tiger, Paper Tiger, and Elephant categories, then ranking urgency as Launch-Blocking, Fast-Follow, or Track to direct mitigation efforts effectively.

Does this risk analysis approach work for cross-functional delivery plans?

Yes, this risk analysis approach works for cross-functional delivery plans by applying backward failure analysis and eight-domain risk coverage to evaluate stakeholder alignment and delivery constraints.

What is the best way to uncover hidden failure risks in a product strategy?

The best way to uncover hidden failure risks in a product strategy is running a structured pre-mortem that converts assumptions, decisions, and constraints into actionable, red-team validated risk outputs.

When should I not use a backward failure analysis for release risk workshops?

Avoid backward failure analysis for release risk workshops if your PMContext lacks defined assumptions, decisions, or constraints, as the pre-mortem requires these inputs to generate actionable risk outputs.