An incident can be resolved before anyone has proved why it happened. This skill applies the Incident Postmortems Specification to keep facts, reported claims, inferences, hypotheses, and decisions separate. It preserves real uncertainty, requires recovery proof, and moves corrective work into durable Engineering Follow-ups instead of a hopeful checklist.
Install for Codex
Download the complete skill package or copy and run:
mkdir -p "${CODEX_HOME:-$HOME/.codex}/skills"
curl -fsSL https://wimdy.works/skills/write-incident-postmortem/bundle.tar.gz \
| tar -xz -C "${CODEX_HOME:-$HOME/.codex}/skills"Install for Claude Code
mkdir -p "$HOME/.claude/skills"
curl -fsSL https://wimdy.works/skills/write-incident-postmortem/bundle.tar.gz \
| tar -xz -C "$HOME/.claude/skills"Invoke directly
$write-incident-postmortem draft a reviewed postmortem from these exact incident records
/write-incident-postmortem draft a reviewed postmortem from these exact incident recordsOr let ACK construct and validate a draft from pinned evidence:
ack incident draft --source record=.ack/incidents/checkout-2026-07.yaml