postmortem

Create blameless postmortem documents with root cause analysis and SMART action items.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/chavangorakh1999/sde-skills --skill postmortem-chavangorakh1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/chavangorakh1999/sde-skills/tree/main/sde-debugging/skills/postmortem
Command: npx skills add https://github.com/chavangorakh1999/sde-skills --skill postmortem-chavangorakh1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams conduct thorough, blameless postmortems after significant incidents to identify root causes and prevent recurrence.

Core Features & Use Cases

  • Blameless Culture: Emphasizes systemic issues over individual blame.
  • Structured Template: Provides a comprehensive template covering impact, timeline, RCA, and action items.
  • SEV Classification: Offers clear guidelines for incident severity levels.
  • Use Case: After a critical service outage, use this Skill to guide the team through documenting the incident, analyzing its root cause using the 5 Whys, and defining actionable steps to improve system resilience.

Quick Start

Use the postmortem skill to document the recent production incident.

Frequently Asked Questions about postmortem

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

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

To conduct a blameless postmortem, analyze the incident impact, reconstruct the timeline, and perform root cause analysis using the 5 Whys to identify systemic contributing factors and define SMART action items.

What is the 5 Whys root cause analysis method in incident response?

The 5 Whys root cause analysis method is an iterative interrogative technique used during incident response to explore the cause-and-effect relationships underlying a problem to identify its systemic root cause.

How do I classify incident severity levels for SRE postmortems?

You classify incident severity levels for SRE postmortems using SEV-1 through SEV-4 classification guidelines, which categorize impact severity to ensure the response and documentation match the incident's urgency.

Can I use this structured template for SEV-1 through SEV-4 incident documentation?

Yes, you can use this structured template for SEV-1 through SEV-4 incident documentation because it includes a comprehensive review checklist and severity classification guidelines covering impact, timeline, RCA, and action items.

What is the best way to define SMART action items during root cause analysis?

The best way to define SMART action items during root cause analysis is to ensure they are Specific, Measurable, Achievable, Relevant, and Time-bound, directly addressing the systemic contributing factors identified.

When should I not use a blameless postmortem approach for incident response?

You should not use a blameless postmortem approach if your goal is assigning individual blame rather than uncovering systemic issues, as the process specifically emphasizes systemic failures and structural contributing factors over individual mistakes.