postmortem

Facilitate structured postmortem analysis using the 5 Whys method.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Fantasia1999/claude-skills-zh --skill postmortem-fantasia1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/Fantasia1999/claude-skills-zh/tree/main/translations/c-level-advisor/executive-mentor/skills/postmortem
Command: npx skills add https://github.com/Fantasia1999/claude-skills-zh --skill postmortem-fantasia1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams conduct effective postmortems to understand the root causes of failures, extract valuable lessons, and implement concrete changes to prevent future occurrences, moving beyond blame and superficial fixes.

Core Features & Use Cases

  • Structured Analysis: Provides a step-by-step framework for dissecting failures, from defining the event to establishing a change log.
  • Root Cause Identification: Guides users through techniques like "5 Whys" to distinguish between contributing factors and true root causes.
  • Preventative Measures: Focuses on identifying actionable changes and setting verification dates to ensure improvements are implemented and effective.
  • Use Case: After a critical service outage, use this Skill to systematically analyze what went wrong, why it happened, and what specific actions the engineering and operations teams need to take to prevent a similar incident in the future.

Quick Start

Use the postmortem skill to analyze 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 structured root cause analysis after a production incident?

Conduct a root cause analysis by defining the incident event, applying the 5 Whys method to distinguish contributing factors from true root causes, and creating an actionable change log with verification dates.

What is the 5 Whys method for identifying the root causes of failures?

The 5 Whys method is a root cause analysis technique used during a postmortem to iteratively ask why an event occurred, helping teams distinguish superficial contributing factors from the true root causes of failures.

How do I distinguish between contributing factors and actual root causes in a postmortem?

In a postmortem, you distinguish contributing factors from actual root causes by systematically analyzing the failure through the 5 Whys method to uncover the fundamental underlying issue rather than surface-level symptoms.

Can I use this structured postmortem framework for project retrospectives and operational reviews?

Yes, you can use this structured postmortem framework for project retrospectives and operational reviews, as it provides a systematic process for event definition, root cause analysis, and establishing preventative actions.

What's the best way to identify missed warning signs during an incident analysis?

The best way to identify missed warning signs during incident analysis is to use a structured postmortem framework that reviews the timeline of events leading up to the failure, ensuring all anomaly indicators are documented.

How do I establish actionable preventative measures for failure prevention after a service outage?

Establish actionable preventative measures for failure prevention by creating a change log during the postmortem that details specific actions, assigns ownership, and sets verification dates to ensure effectiveness.