incident-postmortem

A blameless post-mortem documents the incident timeline, contributing factors, and customer impact without assigning blame. This Skill generates a structured root-cause analysis and appends it to your incident history file.

A structured root-cause analysis includes the incident timeline, contributing factors, customer impact assessment, and action items with assigned owners and due dates. It also requires council sign-off for finalization.

You track action items with owners and due dates by generating a post-mortem document that structures these fields alongside the root-cause analysis. The workflow appends this data to your incident history.

Yes, the workflow uses an append-only history format that preserves original statements. You cannot modify existing entries, but you can add follow-up corrections in separate entries.

Yes, the post-mortem workflow includes a council-facing sign-off process to ensure alignment with operations, security, and engineering governance before the incident entry is finalized.

Maintaining institutional learning requires appending blameless post-mortems to a shared incident history file. This preserves the root-cause analysis and action items for future reference by engineering teams.