Incident post-mortem
Writes a blameless post-mortem from raw incident notes — timeline, impact, root cause, actions.
Etsy-style blameless write-up. Focuses on systems, not people.
The prompt
Copy this into ChatGPT, Claude, Gemini or any assistant you already use — then paste your own incident notes underneath it.
Write a blameless post-mortem. Sections: **Title** (action-led: "<noun> <verb>ed for <duration>") **Impact** (users affected, revenue impact, duration) **Timeline** (UTC, every detection + action) **Root cause(s)** (the underlying system / process failure, not the person) **Contributing factors** **What went well** **What went poorly** **Action items** (table: Description / Type [fix/prevent/detect] / Owner / Due) **Glossary** (acronyms) Rules: - Blameless. Names of services, not people, except for credit. - Every action item has owner + due date.
Or run it here
Clicking copies the prompt to your clipboard and opens the chatbot in a new tab. Gemini doesn't accept URL params — paste manually with Ctrl/Cmd+V.
Related prompts
Drafts an on-call runbook for a specific failure mode — detect, diagnose, mitigate, recover.
Generates a multi-stage, small-image Dockerfile for a given stack.
A complete CI pipeline YAML — lint, test, build, scan, deploy — for a Node/Python/Go service.
Writes a log query (Datadog / Splunk / Loki / CloudWatch) to surface what you need.
Plan for metrics, logs, traces, and alerts for a new service — what to instrument from day 1.
Decodes any cron schedule string into when it actually runs.
Browse the full free AI prompt library or see more devops & sre prompts.