Menu

Individual skill

incident-postmortem-writer

Structures raw incident notes into a blameless postmortem - timeline, root cause, impact, and action items. Use after an incident/outage once the immediate fire is out and it needs to be documented.

skills/security/incident-postmortem-writer/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Turn raw, informal incident notes (timestamps, Slack messages, half-remembered sequence of events) into a structured, blameless postmortem document that captures what happened, why, and what changes as a result.

## When to Use

- After an incident/outage, once it's resolved and needs to be documented.
- Raw notes/timeline exist (from an incident channel, monitoring alerts, or people's recollections) and need to become a coherent document.
- A team wants to standardize postmortem format.

## What to Analyze / Do

1. **Build a clear timeline** — order events chronologically with timestamps where available; note where the timeline has gaps or uncertainty rather than inventing precision that isn't there.
2. **Separate root cause from contributing factors** — the root cause is what actually triggered the incident; contributing factors are things that made it worse or harder to detect/resolve (e.g. "alerting was misconfigured" is a contributing factor to detection delay, not necessarily the root cause of the outage itself).