Pre mortem

Skill ulpi-io/plugin-marketplace/plugins/boshu2/skills/pre-mortem

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.From its SKILL.md

Install

npx -y skills add ulpi-io/plugin-marketplace --skill pre-mortem

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.0 KB, 843 tokens by cl100k_base, as published. Nobody here has run it

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?
Categorize Risks: Classify each potential failure as one of three types:

Tigers: Real problems you personally see that could derail the project
- Based on evidence, past experience, or clear logic
- Should keep you awake at night
- Require action
Paper Tigers: Problems others might worry about, but you don't believe in them
- Valid concerns on the surface, but unlikely or overblown
- Not worth significant resource investment
- Worth documenting to align stakeholders
Elephants: Something you're not sure is a problem, but the team isn't discussing it enough
- Unspoken concerns or assumptions nobody is validating
- Could be real; you're unsure
- Deserve investigation before launch
Classify Tigers by Urgency:

Launch-Blocking: Must be solved before launch
- Example: Core feature broken, regulatory blocker, key customer dependency unmet
Fast-Follow: Must be solved within 30 days post-launch
- Example: Performance issues, secondary features incomplete
Track: Monitor post-launch; solve if it becomes an issue
- Example: Nice-to-have features, edge cases
Create Action Plans: For every Launch-Blocking Tiger:
- Describe the risk clearly
- Suggest a concrete mitigation action
- Identify the best owner (function/person)
- Set a decision/completion date

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

Notes

Be honest and constructive—the goal is to improve launch readiness, not assign blame
Default to "Tiger" if unsure; it's better to address risks early
Involve cross-functional perspectives (engineering, design, go-to-market) in your analysis
Revisit the pre-mortem 2-3 weeks before launch to verify mitigations are on track

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most product growth skills give in 843 tokens

Counted across 728 of the 1,010 authors here whose files we hold, read 2026-08-07

Read product marketing context before asking questionsin 24 of 728, across 18 files
Define the ideal customer profilein 21 of 728, across 3 files
Document a rollback plan before deploymentin 21 of 728, across 12 files
Analyze the codebase to understand the productin 19 of 728, across 1 file
Ask clarifying questions about the value propositionin 19 of 728, across 1 file
Search for companies matching the criteriain 19 of 728, across 1 file
Look for signals of immediate needin 19 of 728, across 1 file
Assign a fit score from one to tenin 19 of 728, across 1 file
Identify the target decision-maker rolein 19 of 728, across 1 file
Suggest a personalized contact strategyin 19 of 728, across 1 file
Provide conversation starters for outreachin 19 of 728, across 1 file
Format results in a scannable markdown templatein 19 of 728, across 1 file

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.