postmortem

Create structured postmortem reports for production incidents with root cause analysis.

4|Updated May 1, 2026
One-click install
npx skills add https://github.com/HigorAlves/orc --skill postmortem-higoralves
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/HigorAlves/orc/tree/main/orc/skills/postmortem
Command: npx skills add https://github.com/HigorAlves/orc --skill postmortem-higoralves

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams systematically analyze and document production incidents, fostering blameless learning and continuous improvement.

Core Features & Use Cases

  • Incident Documentation: Guides users to create detailed, structured postmortem reports after major incidents or near-misses.
  • Blameless Analysis: Emphasizes understanding system failures without assigning blame to individuals.
  • Use Case: After a service outage, a team can use this Skill to compile a comprehensive report, including timeline, root causes, and action items, to prevent recurrence.

Quick Start

Use the postmortem skill to draft an incident report summarizing the recent outage event.

Frequently Asked Questions about postmortem

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

FAQPage Schema
What is a blameless postmortem report for incident analysis?

A blameless postmortem focuses on understanding system failures rather than assigning individual blame. It documents incident timelines, root causes, and action items to promote organizational learning and prevent recurrence of production outages.

How do I document an incident timeline and root cause analysis?

You document an incident timeline by compiling a structured postmortem report that details the sequence of events and contributing factors. This process identifies the root cause across technical and organizational domains to drive accountability and learning.

Can I use this incident analysis approach for near-miss events?

Yes, you can use structured incident analysis for near-miss events. Creating detailed postmortem reports for near-misses helps identify contributing factors and track action items, fostering continuous improvement before a major system failure occurs.

Do I need external dependencies to generate a postmortem report?

No, you do not need external dependencies to generate a postmortem report. This incident analysis approach requires no external tools, focusing entirely on templated documentation to facilitate blameless learning and track action items.

What is the best way to track action items after a system failure?

The best way to track action items after a system failure is by integrating them directly into a structured postmortem report. This ensures accountability by documenting root causes and tracking remediation steps across technical and organizational domains.