post-mortem

Guide blameless post-mortems with Five Whys and actionable summaries.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/devmuslim/pdm-skills --skill post-mortem-devmuslim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-mortem
Source: https://github.com/devmuslim/pdm-skills/tree/main/pdm-metrics-reporting/skills/post-mortem
Command: npx skills add https://github.com/devmuslim/pdm-skills --skill post-mortem-devmuslim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, blameless framework to analyze delivery incidents, missed releases, or production outages, focusing on systemic improvements rather than individual blame.

Core Features & Use Cases

  • Incident Analysis: Guides users through gathering incident data, reconstructing timelines, and performing root cause analysis using the "Five Whys" technique.
  • Actionable Insights: Helps identify contributing factors across process, technical, and communication domains, leading to concrete, actionable items.
  • Shareable Summaries: Facilitates the creation of concise, shareable summaries suitable for broader communication.
  • Use Case: After a critical production bug caused a service outage, use this skill to systematically understand what happened, why it happened, and what steps to take to prevent recurrence.

Quick Start

Use the post-mortem skill to start a blameless review of the recent production incident.

Frequently Asked Questions about post-mortem

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

FAQPage Schema
How do I conduct a blameless post-mortem after a production outage?

A blameless post-mortem systematically guides you through incident data gathering, timeline reconstruction, and Five Whys root cause analysis to identify systemic issues without assigning individual blame. It classifies contributing factors across process, technical, and communication domains to generate actionable items.

What is the Five Whys technique for root cause analysis?

The Five Whys technique is a root cause analysis method used during incident reviews to iteratively ask why an event occurred. It helps move beyond surface-level symptoms to uncover the underlying systemic causes of delivery incidents or production outages.

How do I reconstruct an incident timeline for a missed release?

To reconstruct an incident timeline for a missed release, gather all relevant incident data and chronologically map the events. This structured process review helps identify contributing factors and pinpoint where the delivery failure occurred.

Can I use this process for both delivery incidents and production outages?

Yes, this blameless review process is designed to handle both delivery incidents like missed releases and production outages. It systematically analyzes the timeline and contributing factors to produce shareable summaries and actionable items for systemic improvement.

What's the best way to identify contributing factors after an incident?

The best way to identify contributing factors is to classify them across process, technical, and communication domains during a blameless incident review. Using the Five Whys technique helps uncover these systemic factors rather than focusing on individual mistakes.