post-mortem

You can automate post-mortem documentation by providing incident details like what happened, when it occurred, and who noticed it. The skill generates a structured document covering timelines, impacts, and prevention actions from this input.

A blameless post-mortem is a retrospective focusing on systemic issues rather than individual faults. This skill structures root-cause analysis by automatically assembling incident data into timelines, impact assessments, and action-item tracking using blameless templates.

To construct an incident timeline for a retrospective, input the sequence of events and detection times from your incident. The skill automatically builds a structured timeline and tracks action items for prevention.

Yes, engineering teams can generate structured post-mortems without manual formatting. The skill uses reusable references and templates to standardize the assembly of incident events, impacts, and prevention steps.

For structured incident response documentation, you need to provide basic incident details: what happened, when it occurred, and who noticed the event. The skill then automates the assembly of the full post-mortem document.

Yes, this approach works for tracking action items after a failure by embedding prevention steps directly into the generated post-mortem. It standardizes action-item tracking alongside timeline construction and impact assessment.