Postmortem Analysis

Writing comprehensive postmortems: timeline, root cause, prevention, action items.

48 stars 10 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill postmortem-analysis
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/debugging/skills/postmortem-analysis ~/.claude/skills/postmortem-analysis

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Postmortem Analysis

Creating blameless postmortems to learn and prevent recurrence.

## Context

You are documenting a failure for learning. Postmortems are not blame; they're prevention.

## Domain Context

- **Blameless**: Focus on systems/processes, not individuals
- **Timeline**: Precise sequence of events; when did people notice? Take actions?
- **Root Cause**: What enabled the bug? (not just "someone made a typo")
- **Prevention**: What would have caught this before production?
- **Action Items**: Specific, actionable improvements

## Instructions

1. **Gather Facts**: Collect timeline, logs, team recollection; piece together events
2. **Create Timeline**: When did each event occur? Label in 5-minute intervals
3. **Document Context**: What was the system state? Load? Recent changes?
4. **RCA**: Use 5 Whys or fishbone to identify root cause
5. **Prevention**: What would have caught this? Better tests? Monitoring? Design change?
6. **Write Postmortem**: Clear, factual narrative; no blame
7. **Define Action Items**: Specific, assignable, measurable improvements

## Anti-Patterns

- Blame-driven postmortems; focus on systems, not people
- Too much focus on "what" without "why"; understanding enables prevention
- No action items; analysis without improvement is waste
- Same action items as last postmortem; you're repeating the cycle
- Rushed postmortems without facts; gather data before writing

## Further Reading
Read the full skill on GitHub

Details

Skill name
postmortem-analysis
Path
engineer/debugging/skills/postmortem-analysis/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Postmortem Analysis skill do?

Writing comprehensive postmortems: timeline, root cause, prevention, action items.

How do I install the Postmortem Analysis skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Postmortem Analysis popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.