phuryn/pm-skills

pre-mortem

Run a pre-mortem risk analysis on a PRD or launch plan.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/phuryn/pm-skills --skill pre-mortem

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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

Verwandte Aufgaben

aus demselben Repository

Weitere Skills

Alle Skills
phuryn
Community

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

Installationen / 1h
4
GitHub Stars
28.056
Aktualisiert
8. Nov.
phuryn
Community

ansoff-matrix

Generate 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.

Installationen / 1h
2
GitHub Stars
28.018
Aktualisiert
8. Nov.
phuryn
Community

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

Installationen / 1h
2
GitHub Stars
28.018
Aktualisiert
8. Nov.
phuryn
Community

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

Installationen / 1h
2
GitHub Stars
28.018
Aktualisiert
8. Nov.