post-mortem

Analyze failure incidents to identify root causes and generate lessons learned.

3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/carlkibler/agent-skills --skill post-mortem-carlkibler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-mortem
Source: https://github.com/carlkibler/agent-skills/tree/main/skills/post-mortem
Command: npx skills add https://github.com/carlkibler/agent-skills --skill post-mortem-carlkibler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams analyze and reconstruct failure incidents to identify root causes and gather actionable insights, reducing recurrence of similar issues.

Core Features & Use Cases

  • Failure Analysis: Guides users through incident data collection and timeline reconstruction.
  • Root Cause Identification: Applies techniques like the 5 Whys to uncover systemic issues.
  • Use Case: After a production outage, use this Skill to analyze what went wrong, determine systemic weaknesses, and compile lessons learned for future prevention.

Quick Start

Run the post-mortem skill to analyze the recent failure incident and generate a detailed report.

Frequently Asked Questions about post-mortem

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

FAQPage Schema
How do I conduct a blameless post-mortem after a production outage?

A blameless post-mortem analyzes failure incidents by reconstructing timelines and applying techniques like the 5 Whys to identify systemic root causes, rather than assigning individual blame, to generate actionable lessons learned.

What is the best way to identify root causes of recurring process failures?

Identifying root causes of process failures requires structured incident data collection and timeline reconstruction to uncover systemic issues, helping teams prevent similar problems from recurring in the future.

How does the 5 Whys technique work for failure analysis and incident reconstruction?

The 5 Whys technique works for failure analysis by guiding teams through iterative questioning of incident data to uncover underlying systemic issues, enabling accurate timeline reconstruction and effective root cause identification.

Can I use this incident reconstruction approach for bug analysis and process failures?

Yes, you can use this incident reconstruction approach for bug analysis and process failures, as it requires structured incident data to analyze what went wrong and compile lessons learned for future prevention.

What structured incident data do I need to perform a thorough failure analysis?

Performing a thorough failure analysis requires structured incident data related to the event, which is then used to reconstruct timelines, identify systemic weaknesses, and generate actionable lessons learned to improve resilience.

When should I not use a post-mortem for incident analysis?

You should not use a post-mortem when you lack structured incident data for analysis, or when follow-up analysis cannot be performed to validate the identified root causes and implement preventive measures.