postmortem-writing

Draft blameless incident postmortems with root cause analysis and action items.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill postmortem-writing-jhabbig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem-writing
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/plugins/wshobson/incident-response/skills/postmortem-writing
Command: npx skills add https://github.com/Jhabbig/Habbig --skill postmortem-writing-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn incidents into clear, blameless postmortems that explain what happened, why it happened, and how to prevent it from recurring.

Core Features & Use Cases

  • Root Cause Analysis: Organize proximate causes, contributing factors, and deeper systemic issues into a coherent incident narrative.
  • Timeline and Impact Reporting: Capture precise event ordering, customer impact, detection gaps, response actions, and recovery details.
  • Action Item Planning: Produce practical follow-up work with owners, priorities, and due dates so lessons become durable improvements.
  • Use Case: After a production outage, use this Skill to draft the review document, summarize the incident for leadership, and create remediation tasks for engineering and operations.

Quick Start

Draft a blameless postmortem for this incident using the timeline, impact, root cause analysis, lessons learned, and action items.

Frequently Asked Questions about postmortem-writing

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

FAQPage Schema
How do I write a blameless postmortem after a production outage?

Writing a blameless postmortem involves organizing proximate causes, contributing factors, and systemic issues into a coherent narrative. This Skill requires structured evidence and chronological event ordering to produce a review document with actionable follow-up items.

What is a blameless incident review and when do I need one?

A blameless incident review focuses on systemic issues rather than individual mistakes to drive learning. You need one after a SEV1 or SEV2 production incident, a near-miss, or any event requiring durable engineering and operations improvements.

How do I document a root cause analysis with action items for an incident?

Documenting a root cause analysis requires capturing proximate causes, detection gaps, and response actions. This Skill organizes these factors into an incident narrative and generates prioritized action items with assigned owners and due dates.

Can I use this for near-miss analyses and SEV1 incident writeups?

Yes, this Skill supports near-miss analyses, SEV1 incident writeups, and SEV2 document drafting. It processes structured evidence to facilitate learning-focused incident meetings and produce leadership impact summaries.

What is the best way to structure an incident timeline for a postmortem?

The best way to structure an incident timeline is through precise chronological event ordering. This Skill captures detection gaps, customer impact, response actions, and recovery details to build a coherent timeline for your postmortem.

How do I create prioritized action items with owners for incident remediation?

Creating prioritized action items requires converting lessons learned into durable improvements. This Skill generates practical follow-up work with assigned owners, priorities, and due dates to ensure accountability for remediation tasks.