postmortem

Conduct structured incident post-mortems with root cause analysis and preventive fixes.

127|22|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/flonat/flonat-research --skill postmortem-flonat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/flonat/flonat-research/tree/main/skills/postmortem
Command: npx skills add https://github.com/flonat/flonat-research --skill postmortem-flonat

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill aids in creating structured post-mortem reports after incidents, mistakes, or stuck sessions, ensuring systematic improvement and preventing future occurrences.

Core Features & Use Cases

  • Structured Analysis: Offers a structured framework for analyzing incidents, identifying root causes, and implementing preventive measures.
  • Timeline Reconstruction: Assists in building a chronological sequence of events to understand the sequence of actions leading to the incident.
  • Root Cause Analysis: Utilizes the 5 Whys method to pinpoint the root cause and suggest concrete changes.
  • Fix Classification: Categorizes fixes into skill, guard, rule, documentation, hook, or checklist, ensuring appropriate implementation.
  • Fix Implementation: Encourages immediate implementation of fixes during the retrospective phase.
  • Verification: Defines test scenarios and success criteria to verify the effectiveness of the fixes.
  • Output: Writes a comprehensive report detailing the incident, root cause, contributing factors, and implemented fixes.

Quick Start

Start a post-mortem for the incident "Server downtime on January 5th" by running the command: /postmortem start incident "Server downtime on January 5th".

Frequently Asked Questions about postmortem

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

FAQPage Schema
How do I conduct a root cause analysis for an incident?

Conduct root cause analysis by reconstructing the incident timeline and applying the 5 Whys method to pinpoint the underlying cause, enabling systematic process improvement and future incident prevention.

What is the best way to structure a post-mortem report after a system outage?

A structured post-mortem report documents the chronological sequence of events, identifies contributing factors, and categorizes fixes into skills, guards, rules, or checklists to ensure appropriate implementation.

Can I implement and verify incident fixes during the retrospective phase?

You can implement fixes during the retrospective phase and verify their effectiveness by defining test scenarios and success criteria to ensure the root cause is fully mitigated.

How do I categorize preventive measures in incident management?

Categorize preventive measures in incident management by classifying fixes as skill, guard, rule, documentation, hook, or checklist types, ensuring appropriate implementation and systematic process improvement.

When do I need a systematic post-mortem for process improvement?

You need a systematic post-mortem for process improvement after experiencing incidents, mistakes, or stuck sessions to analyze root causes, implement preventive measures, and prevent future occurrences.

Does postmortem require specific tools to start an incident analysis?

Postmortem does not require external dependencies to start incident analysis, but requires analysis and documentation skills to build timelines, implement fixes, and verify effectiveness.