Postmortem
Use this skill after incidents, major repeated tool failures, rollback events, security findings, data issues, monitoring failures, or repeated regression loops.
Workflow
- Keep the write-up blameless and system-focused.
- Capture objective impact and detection source.
- Build a timeline from logs, commits, deploys, alerts, and human actions.
- Separate trigger, contributing factors, and root causes.
- Write corrective actions with owners, priority, and verification.
- Update
docs/harness/POSTMORTEM_TEMPLATE.md. - Link follow-ups in
docs/harness/RISKS.md,docs/harness/DECISIONS.md, anddocs/harness/OPERATIONS_RUNBOOK.md.
Required Sections
- Summary
- Impact
- Detection
- Timeline
- Root causes
- What went well
- What went poorly
- Corrective actions
- Prevention checks
Required Output
Return postmortem status, missing evidence, corrective actions, and whether follow-up work should block release.