pm-postmortem-writer

Name: pm-postmortem-writer
Availability: InStock
Author: zephyrwang6

Generate structured postmortem reports from launch goals, timeline records, and outcome data.

14|4|Updated Mar 31, 2026

Search Tags:#root cause analysis #product management #retrospective #action items #postmortem #launch review

Ready to run

npx skills add https://github.com/zephyrwang6/allSkills --skill pm-postmortem-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-postmortem-writer
Source: https://github.com/zephyrwang6/allSkills/tree/main/pm-postmortem-writer
Command: npx skills add https://github.com/zephyrwang6/allSkills --skill pm-postmortem-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps turn scattered launch notes, metrics, and incident records into a structured postmortem report that explains what happened, why it happened, and what should change next.

Core Features & Use Cases

Goal-vs-result review: Compares planned objectives with actual outcomes and highlights gaps with concrete numbers.
Root-cause analysis: Uses 5-Why, timeline analysis, and related methods to trace deviations back to controllable causes.
Lessons and actions: Captures what went well, what should stop, and assigns clear owners and deadlines for follow-up actions.
Use cases: Version launches, feature rollouts, incident RCA reports, OKR retrospectives, quarterly reviews, and A/B experiment summaries.

Quick Start

Ask the Skill to write a postmortem from your launch goals, timeline, results, issues, and owners, and it will return a structured report with action items.

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 postmortem report for a product launch?▼

To write a postmortem report, provide your launch goals, timeline records, outcome data, and issue lists. The process generates a structured document comparing planned objectives against actual results and assigning action items.

What is root cause analysis in a retrospective?▼

Root cause analysis in a retrospective traces deviations back to controllable causes using methods like 5-Why and timeline analysis. It identifies why specific issues occurred during a launch or incident to prevent recurrence.

Can I use a postmortem template for OKR retrospectives and A/B experiment summaries?▼

Yes, you can use a postmortem template for OKR retrospectives and A/B experiment summaries. The process adapts to feature rollouts and quarterly reviews by comparing goal-versus-result data and extracting lessons learned.

What is the best way to document action items with owners and deadlines?▼

The best way to document action items is to capture what went well, what should stop, and assign clear owners and deadlines for follow-up actions. This ensures accountability after the root cause analysis is complete.

Does incident root cause analysis require goal-versus-result comparison?▼

Yes, incident root cause analysis requires goal-versus-result comparison to highlight gaps with concrete numbers. This comparison contextualizes the incident's impact and frames the subsequent 5-Why investigation.

What do I need to generate a structured launch review?▼

To generate a structured launch review, you need launch goals, timeline records, outcome data, and issue lists. These inputs enable the system to perform multi-layer root-cause analysis and produce actionable follow-up steps.