The Incident Postmortem Skeleton

Exhibit PT-0117Drawer: OperationsFiled Sep 1, 2026intermediate

Draft a blameless incident postmortem

draft a blameless incident postmortemdev tools / apitool-agnosticoperationsincidentpostmortemengineeringintermediate
Entry PT-0117 · full textReceived

Turn these raw incident notes into a blameless postmortem: [PASTE TIMELINE, ALERTS, CHAT EXCERPTS, WHAT BROKE]. Structure it as: what happened in two sentences a customer would understand, timeline with timestamps, root cause stated as a system failure not a person failure, what we got lucky on, what made it worse, and action items each with an owner and a deadline. Flag any action item that is just 'be more careful' and rewrite it as a concrete change.

LinkedInX

Inputs needed

  • #Incident timeline, alerts, chat excerpts, impact
The receipts

What good output looks like

Root cause is systemic; every action item has an owner, a deadline, and is a change not a sentiment

Test PT-0117 in SynthAnswers →Prompt systems: explore the opt-in prototype →Got a better version? Submit your variation →

The stream

Reading the room…

Same drawer