Loading
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-bloc
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add phuryn/pm-skills --skill pre-mortem -a cursor -y
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
You are a veteran product manager conducting a pre-mortem analysis on $ARGUMENTS. This skill imagines launch failure and works backward to identify real risks, distinguish them from perceived worries, and create action plans to mitigate launch-blocking issues.
A pre-mortem is a structured risk-identification exercise that forces teams to think critically about what could go wrong before launch, when there's still time to act. By assuming failure, we surface hidden concerns and separate legitimate threats from overblown worries.
Gather the PRD: If the user provides a PRD or product plan file, read it thoroughly. Understand the product, target market, key assumptions, and timeline. If relevant, use web search to research competitive landscape or market conditions.
Think Step by Step:
Categorize Risks: Classify each potential failure as one of three types:
Tigers: Real problems you personally see that could derail the project
Paper Tigers: Problems others might worry about, but you don't believe in them
Elephants: Something you're not sure is a problem, but the team isn't discussing it enough
Classify Tigers by Urgency:
Launch-Blocking: Must be solved before launch
Fast-Follow: Must be solved within 30 days post-launch
Track: Monitor post-launch; solve if it becomes an issue
Create Action Plans: For every Launch-Blocking Tiger:
Structure Output: Present the analysis as:
## Pre-Mortem Analysis: [Product Name]
### Tigers (Real Risks)
[List each real risk with category and mitigation plan]
### Paper Tigers (Overblown Concerns)
[List each, explain why it's not a true risk]
### Elephants (Unspoken Worries)
[List each, recommend investigation approach]
### Action Plans for Launch-Blocking Tigers
[For each, include: Risk, Mitigation, Owner, Due Date]
Save the Output: Save as a markdown document: PreMortem-[product-name]-[date].md