autopsy

A blameless post-mortem identifies what happened, its impact, and follow-up actions without attributing fault. It reconstructs timelines and uses 5 Whys analysis to document root causes and generate preventative action items in a structured report.

The 5 Whys root-cause analysis identifies underlying failures by iteratively asking why an incident occurred. It moves beyond surface symptoms to reveal the true root cause for inclusion in blameless post-mortem documentation and action-item planning.

Reconstructing an incident timeline requires mapping chronological events and their operational impacts. This timeline reconstruction provides the factual baseline for root-cause analysis and structured post-mortem reporting for engineering, ops, and product teams.

Yes, blameless post-mortems can be generated for engineering, ops, and product teams. The process works across incident response scenarios, enabling timeline reconstruction and action-item driven reporting saved as a structured Markdown document.

The best way to document action items is through a structured post-mortem report saved as Markdown under .workspace/shared/postmortems. This action-item driven documentation ensures follow-up tasks are tracked to prevent incident recurrence across teams.