postmortem

Generates structured, blameless postmortems for incident reviews.

13|4|Updated Feb 20, 2026

Search Tags:#timeline #postmortem #root-cause-analysis #incident-management #blameless #action-items

Ready to run

npx skills add https://github.com/OmexIT/claude-skills-pack --skill postmortem-omexit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/OmexIT/claude-skills-pack/tree/main/skills/postmortem
Command: npx skills add https://github.com/OmexIT/claude-skills-pack --skill postmortem-omexit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incident reviews are often inconsistent and blame-driven. This Skill generates structured, blameless postmortems that document timelines, customer impact, root causes, contributing factors, detection gaps, and prioritized action items.

Core Features & Use Cases

Structured postmortem templates for rapid documentation after incidents
Capture precise timelines, impacts, and root-cause information
Identify contributing factors and detection gaps, culminating in actionable items for prevention

Quick Start

Provide a title for the incident and relevant details to generate a complete blameless postmortem document.

Frequently Asked Questions about postmortem

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

FAQPage Schema

How do I write a blameless postmortem for an incident review?▼

A blameless postmortem documents incident timelines, customer impact, and root causes without assigning blame. It captures contributing factors, detection gaps, and prioritized action items to prevent recurrence.

What should be included in a root-cause analysis for an outage?▼

Root-cause analysis for an outage should include a precise incident timeline, customer impact, evidence-backed root causes, contributing factors, detection gaps, and prioritized action items with assigned owners and deadlines.

How do I document near-misses in software incident management?▼

Document near-misses by generating a structured postmortem that captures the timeline, detection gaps, and contributing factors, culminating in clearly assigned action items to prevent future incidents.

Can I automate postmortem template generation for incident reviews?▼

Yes, you can generate structured postmortem templates by providing an incident title and relevant details. This produces a complete document with timelines, impact, root causes, and action items.

What is the best way to assign owners and deadlines for incident action items?▼

The best way to assign action items is within a structured postmortem, ensuring every preventative measure has a clearly assigned owner, a deadline, and defined verification criteria.