Is this skill aligned with industry standards?

Yes, it is grounded in Site Reliability Engineering (SRE) guidelines, SWEBOK, and NIST standards for incident reporting.

What are the common postmortem anti-patterns this skill avoids?

The skill helps avoid blame-driven analysis, rushing the report without data, and failing to define specific, measurable action items.

What is a blameless postmortem?

A blameless postmortem is a document that focuses on systemic failures and process improvements rather than assigning fault to individuals for mistakes.

How does this skill assist with Root Cause Analysis?

It provides structured guidance using methodologies like the '5 Whys' or Fishbone diagrams to look past human error and find the underlying technical or organizational causes.

Postmortem Analysis

Name: Postmortem Analysis
Author: sethdford

bysethdford

•

Analytics & Monitoring

Generates blameless, standards-grounded postmortem reports to identify root causes and prevent incident recurrence.

Postmortem Analysis provides a structured framework for documenting system failures and service outages within the Claude Code environment. By focusing on systems rather than individuals, it guides users through gathering facts, constructing precise timelines, and performing Root Cause Analysis (RCA) using methodologies like the '5 Whys.' This skill ensures that technical teams move beyond superficial fixes to implement actionable, measurable improvements that strengthen infrastructure and prevent future regressions, grounded in SRE and SWEBOK principles.

Key Features

0111 GitHub stars

02Blameless incident documentation framework

03SRE-aligned reporting standards for production failures

04Precise 5-minute interval event timeline construction

05Prevention strategy and actionable improvement generation

06Root Cause Analysis (RCA) via 5 Whys and Fishbone methodologies

Use Cases

01Analyzing a software regression to identify gaps in automated testing

02Documenting a production service outage or critical performance degradation

03Facilitating team learning sessions after security incidents or data breaches

Key Features

0111 GitHub stars

02Blameless incident documentation framework

03SRE-aligned reporting standards for production failures

04Precise 5-minute interval event timeline construction

05Prevention strategy and actionable improvement generation

06Root Cause Analysis (RCA) via 5 Whys and Fishbone methodologies

Use Cases

01Analyzing a software regression to identify gaps in automated testing

02Documenting a production service outage or critical performance degradation

03Facilitating team learning sessions after security incidents or data breaches