pm-postmortem-writer

Generate structured postmortem reports with 5-Why root cause analysis and assigned action items.

14|4|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/SpaceZephyr/allSkills --skill pm-postmortem-writer-spacezephyr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-postmortem-writer
Source: https://github.com/SpaceZephyr/allSkills/tree/main/pm-postmortem-writer
Command: npx skills add https://github.com/SpaceZephyr/allSkills --skill pm-postmortem-writer-spacezephyr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Product teams frequently waste time on unstructured postmortems that lack data-backed conclusions, clear issue ownership, and actionable follow-ups, leading to repeated mistakes and no tangible process improvement.

Core Features & Use Cases

  • 5-Stage Structured Workflow: Guides users through information intake, goal vs. actual result comparison, root cause analysis, lessons learned extraction, and actionable item generation to ensure no critical step is missed.
  • Multi-Scenario Support: Tailored templates and guidance for version launch postmortems, P0/P1 incident RCA reports, OKR reviews, quarterly retrospectives, and A/B experiment evaluations.
  • Built-in Quality Guardrails: Includes a 10-point quality checklist, 5-Why root cause analysis framework with responsibility attribution, and fallback strategies for incomplete input to ensure report consistency and actionability.
  • Use Case Example: For a delayed feature launch with 7% lower-than-expected DAU growth, the skill generates a full report with quantified performance gaps, root cause breakdowns, and assigned action items with clear deadlines and success criteria.

Quick Start

Use the pm-postmortem-writer skill to generate a structured postmortem report for the Q3 user growth feature launch using the provided launch metrics, issue list, and original project goals.

Frequently Asked Questions about pm-postmortem-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a structured product postmortem report with clear action items?

To write a structured product postmortem, use a 5-stage workflow: information intake, goal versus actual result comparison, root cause analysis, lessons learned extraction, and actionable item generation with assigned owners and deadlines.

What is the best way to conduct root cause analysis for a P0 or P1 incident?

The best way to conduct root cause analysis for a P0 or P1 incident is applying the 5-Why framework with responsibility attribution to break down issues and generate an incident report with quantified performance gaps.

Can I use a retrospective template for quarterly OKR reviews and A/B test evaluations?

Yes, you can use tailored retrospective templates for quarterly OKR reviews and A/B test evaluations to compare quantified goals against actual results and extract reusable lessons learned from experiment iterations.

How do I ensure my version launch postmortem includes data-backed conclusions?

To ensure your version launch postmortem includes data-backed conclusions, apply a 10-point quality checklist and fallback strategies for incomplete input to verify quantified goal comparisons and clear issue ownership.

What should I do if my incident report has incomplete input data for root cause analysis?

If your incident report has incomplete input data for root cause analysis, apply built-in fallback strategies to fill gaps and maintain report consistency, ensuring the 5-Why analysis still produces actionable follow-up items.