Mmcp.market

pre-mortem skill

by phuryn·phuryn/pm-skills·27k stars·MIT

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.

A100/100content scan

Is the pre-mortem skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the pre-mortem skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-execution/skills/pre-mortem ~/.claude/skills/pre-mortem
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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

  1. 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.
  1. 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?
  1. 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
  1. 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
  1. 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
  1. 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]
  1. 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

Further Reading

  • How Meta and Instagram Use Pre-Mortems to Avoid Post-Mortems
  • How to Manage Risks as a Product Manager

More skills from phuryn/pm-skills

  • Aab-test-analysisAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
  • Aanalyze-feature-requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
  • Aansoff-matrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
  • Abeachhead-segmentIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
  • Abrainstorm-experiments-existingDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
  • Abrainstorm-experiments-newDesign lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
  • Abrainstorm-ideas-existingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
  • Abrainstorm-ideas-newBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
  • Abrainstorm-okrsBrainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
  • Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
  • Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
  • Acohort-analysisPerform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.

All agent skills → · MCP servers