
Pre Mortem
This runs a structured pre-mortem on your PRD or launch plan by imagining the product fails in 14 days and working backward to find what went wrong. It categorizes risks into Tigers (real problems worth losing sleep over), Paper Tigers (overblown worries that sound scary but aren't), and Elephants (things nobody's talking about but should be). Launch-blocking Tigers get concrete mitigation plans with owners and dates. The framework is stolen from how Meta and Instagram do launch planning, and it's genuinely useful for surfacing the risks your team is too polite or too busy to mention in planning meetings. Best used a few weeks before launch when you still have time to fix things.
- install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.
- 5
- skills.sh installs
- 10.5K
- GitHub stars
- 27.8K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add phuryn/pm-skills --skill pre-mortem --agent claude-codeInstalls into .claude/skills of the current project.
Files
Pre-Mortem: Risk Analysis for Product Launch
Purpose
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.
Context
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.
Instructions
-
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:
- Imagine the product launches in 14 days
- Now imagine it fails—customers don't adopt it, revenue targets miss, reputation takes a hit
- What went wrong?
- What did we miss or not execute well?
- What were we overconfident about?
Sponsors
Details
- Repository
- github.com/phuryn/pm-skills
- Categories
- Testing & QA, Productivity & Planning
- First seen
- May 16, 2026
More from phuryn/pm-skills
All 68- Prioritization Frameworks10.2K
- Outcome Roadmap10.1K
- Strategy Red Team9.5K
- Competitor Analysis4.1K
- Business Model3.9K
- Privacy Policy3.7K
- Brainstorm Ideas New3.5K
- User Stories3.4K
- Startup Canvas3.4K
- Gtm Strategy3.3K
- Product Name3.3K
- Product Strategy3.3K
- Monetization Strategy3.3K
- Value Proposition3.3K
- Sentiment Analysis3.2K
- Customer Journey Map3.2K
- Summarize Meeting3.2K
- Brainstorm Ideas Existing3.2K
- Swot Analysis3.2K
- Metrics Dashboard3.1K
- Opportunity Solution Tree3.1K
- Grammar Check3.1K
- Ideal Customer Profile3.1K
- Market Sizing3.1K