Post-Mortem Process

Deliver a complete post-incident review workflowbba, from data collection to actionable recommendations, with this tool.

4|1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/lapc506/flutter-agentic-boilerplate --skill post-mortem-process-lapc506
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Post-Mortem Process
Source: https://github.com/lapc506/flutter-agentic-boilerplate/tree/main/skills/system-reliability-engineering/post-mortem
Command: npx skills add https://github.com/lapc506/flutter-agentic-boilerplate --skill post-mortem-process-lapc506

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive framework and tools to conduct thorough, blameless post-mortems after incidents, ensuring that lessons are learned and preventative actions are taken.

Core Features & Use Cases

  • Structured Analysis: Guides users through a detailed incident review process, from detection to resolution and follow-up.
  • Blameless Culture: Promotes a safe environment for open discussion and learning by focusing on systems and processes, not individuals.
  • Actionable Insights: Helps identify root causes, contributing factors, and generates clear, trackable action items to prevent future occurrences.
  • Use Case: After a critical service outage, use this Skill to generate a post-mortem document, identify the root cause (e.g., a configuration error in a new deployment), and create action items to improve monitoring and deployment validation.

Quick Start

Initiate a post-mortem analysis for the recent outage using the provided template and guidelines.

Frequently Asked Questions about Post-Mortem Process

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

FAQPage Schema
How do I conduct a blameless post-mortem analysis after a system incident?

To conduct a blameless post-mortem, guide your team through a structured incident review from detection to resolution, focusing on systems and processes rather than individuals. This approach identifies root causes and generates trackable action items to prevent recurrence.

What is the best way to track action items identified during root cause analysis?

The best way to track action items from root cause analysis is using a structured post-mortem template that documents contributing factors and clear follow-up tasks. This transforms incident insights into trackable preventative actions for continuous improvement.

Does this incident management process work for reviewing critical service outages?

Yes, this incident management process works for reviewing critical service outages by facilitating comprehensive data collection and root cause identification. It helps generate detailed post-mortem documents to validate deployments and improve monitoring.

How do I foster a blameless SRE culture when documenting lessons learned?

Fostering a blameless SRE culture when documenting lessons learned requires using structured post-mortem guidelines that focus on systemic vulnerabilities rather than individual errors. This creates a safe environment for open discussion and continuous improvement.

Can I automate post-mortem data collection for incident management?

Yes, you can automate post-mortem data collection for incident management using the provided automation scripts and structured templates. This streamlines comprehensive incident review by integrating guidelines and automated data extraction.

What limitations exist when using PDF parsing dependencies for incident review?

When using PDF parsing dependencies like pypdf, pdfplumber, and pdf2image for incident review, limitations depend on the input data format. The process works best when incident data is structured for automated extraction before the root cause analysis begins.