Blameless post-mortem write-up template. Claude Sonnet.
Modality
Text
Model
claude-sonnet-4-6
Write a blameless post-mortem for the following incident:
Incident: {{incident_summary}}
Detected: {{detection}}
Resolution: {{resolution}}
User impact: {{user_impact}}
Output sections in this order: Summary (3 sentences, no jargon), Timeline (UTC timestamps, factual only), Root cause (the technical chain — don't stop at the proximate cause, ask 'why?' until you reach a process or design decision), What went well, What went wrong (no individuals named — talk about systems, tests, alerts, runbooks), Action items (each one specific, assigned, dated).The 'ask why until you reach a process decision' nudge prevents stop-short causes like 'a developer made a typo'. Blameless framing is the point.
Embed
Visitors see the card and can run the prompt on Artinstring with their own account.
<iframe src="https://artinstring.com/embed/code-postmortem" width="100%" height="420" loading="lazy" style="border:0;border-radius:16px;" title="Engineering Post-Mortem · Artinstring"></iframe>More from Writers' Toolkit
Draft a 'what-to-do-with-this' section for a newsletter, after the news bit (Sonnet 4.6).
in Writers' Toolkit
Translate a half-formed PR comment into one that's direct, kind, and unambiguous (Sonnet 4.6).
in Writers' Toolkit
Generate a tailored design critique checklist for a specific surface (Sonnet 4.6).
in Writers' Toolkit