Post-Mortem Process

Guide blameless post-mortems with timeline reconstruction and 5 Whys analysis.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/vertivolatam/monorepo --skill post-mortem-process
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Post-Mortem Process
Source: https://github.com/vertivolatam/monorepo/tree/main/skills/system-reliability-engineering/post-mortem
Command: npx skills add https://github.com/vertivolatam/monorepo --skill post-mortem-process

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured, blameless process for analyzing incidents, identifying root causes, and defining actionable steps to prevent future occurrences, thereby improving system reliability and team learning.

Core Features & Use Cases

  • Incident Analysis: Facilitates a deep dive into what happened during an incident, including timeline reconstruction and impact assessment.
  • Root Cause Identification: Employs techniques like the "5 Whys" to uncover underlying systemic issues, not just surface-level problems.
  • Action Item Generation: Ensures clear, trackable action items are created with owners and deadlines to address identified weaknesses.
  • Blameless Culture Promotion: Guides teams to focus on learning and system improvement rather than assigning blame.
  • Use Case: After a critical service outage (SEV1), use this Skill to guide the team through a blameless post-mortem meeting, document the incident, identify contributing factors, and create follow-up tasks to enhance system resilience.

Quick Start

Initiate a blameless post-mortem process for the recent outage.

Frequently Asked Questions about Post-Mortem Process

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

FAQPage Schema
What is a blameless post-mortem process in incident management?

A blameless post-mortem process is a structured incident management technique that reconstructs timelines and identifies root causes to improve system reliability, focusing on learning from failures rather than assigning individual blame.

How do I conduct root cause analysis for a system outage using the 5 Whys technique?

To conduct root cause analysis using the 5 Whys technique, repeatedly ask why an incident occurred to drill down past surface-level symptoms. This reveals underlying systemic issues and generates trackable action items to prevent recurrence.

When do I need to perform a post-mortem after an incident?

You need to perform a post-mortem after any critical system incident, such as a SEV1 outage, to document the timeline, assess impact, and create follow-up tasks that enhance overall system resilience and prevent future failures.

Does this incident management process work for SRE teams fostering continuous improvement?

Yes, this process specifically supports SRE and engineering teams by enforcing blameless principles and structured documentation, which fosters a culture of continuous improvement and turns incident learnings into actionable systemic fixes.

What is the best way to document incident timelines and track action items for reliability?

The best way to document incident timelines and track action items is through a structured post-mortem framework that records chronological events, assigns clear owners and deadlines to follow-up tasks, and captures lessons learned for future reference.

What are the limitations of a blameless post-mortem approach for incident analysis?

The limitations of a blameless post-mortem approach include the strict requirement for team adherence to blameless principles and the necessity of disciplined, structured documentation to ensure identified root causes translate into tracked systemic improvements.