pre-mortem runs a risk analysis on a PRD or launch plan by assuming the product launches in 14 days and then fails. It works backward to what went wrong and sorts each risk into one of three types: Tigers are real problems, Paper Tigers are overblown worries and Elephants are concerns the team is not discussing.
Tigers are then classed as launch-blocking, fast-follow within 30 days, or track, and every launch-blocking Tiger gets a mitigation, an owner and a due date.
What You Get
- A Tigers list with a category and mitigation plan for each real risk
- A Paper Tigers list that explains why each concern is not a true risk
- An Elephants list with a suggested way to investigate each one
- An action plan table for launch-blocking Tigers with risk, mitigation, owner and due date
- A markdown file named PreMortem-[product-name]-[date].md
Common Use Cases
- Stress-testing a PRD two weeks before launch
- Aligning stakeholders on which worries deserve resources
- Surfacing unspoken concerns before a go or no-go decision
What Makes It Unique
It adds the Elephant category for risks the team is quietly avoiding, and it separates Tigers by urgency so only launch-blocking items demand an owner and a date. It also points to the live-qa skill as a way to collect risks anonymously from the team.
Under The Hood
The skill is one SKILL.md of instructions with no scripts. The agent reads the PRD or plan file you provide and may use web search to research the competitive landscape or market conditions. It saves the analysis as a markdown file in your working folder.