incident-postmortem

Generate a Markdown postmortem with 5-whys, timeline, and action items.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Eric-Pacheco95/claude-workbench --skill incident-postmortem-eric-pacheco95
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-postmortem
Source: https://github.com/Eric-Pacheco95/claude-workbench/tree/main/.claude/skills/incident-postmortem
Command: npx skills add https://github.com/Eric-Pacheco95/claude-workbench --skill incident-postmortem-eric-pacheco95

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill solves the challenge of conducting a structured and blameless incident postmortem process after a system incident.

Core Features & Use Cases

  • Blameless Facilitation: Ensures the incident investigation is conducted in a non-blaming environment.
  • Structured Output: Automatically generates a document that outlines the timeline, root cause analysis, and action items.
  • Automated Analysis: Conducts a 5-why analysis for root cause identification.

Quick Start

To begin an incident postmortem, run /incident-postmortem <incident description>.

Frequently Asked Questions about incident-postmortem

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

FAQPage Schema
How do I conduct a blameless postmortem after an incident?

To conduct a blameless postmortem, you input resolved incident details to automatically generate a structured Markdown document containing the timeline, 5-whys root cause analysis, and action items.

What is the 5-whys root cause analysis method for incident management?

The 5-whys root cause analysis method iteratively asks why an incident occurred to identify fundamental systemic issues. This Skill automates that process to find root causes without assigning individual blame.

How do I generate an incident postmortem document automatically?

You generate an incident postmortem document automatically by running the command with your incident description. The Skill processes the details and outputs a structured Markdown file summarizing the event.

When should I start the incident postmortem process?

You should start the incident postmortem process only after incident resolution has occurred. The Skill assumes the incident is resolved and requires incident details as input to begin the analysis.

What is the best way to structure action items from a root cause analysis?

The best way to structure action items from root cause analysis is to automate their generation alongside the incident timeline. This Skill outputs a structured Markdown file containing the resulting action items.

Can I use this postmortem process for incidents that are still ongoing?

No, you cannot use this postmortem process for incidents that are still ongoing. The Skill explicitly assumes that incident resolution has already occurred and requires details of the resolved event as input.