AI Prompt for Incident Postmortem Reports
Turn incident notes into a structured, blameless postmortem with timeline, root cause chain, and concrete action items.
What it does
Takes your raw incident notes — Slack messages, on-call logs, timestamps, whatever you have — and produces a structured postmortem document. The key differentiator: it enforces blameless language, separates contributing factors from the root cause, and generates action items that are specific enough to actually track.
Example output
A 3–4 line excerpt of what this prompt produces.
Root Cause Chain: 1. The deployment pipeline does not enforce schema migration verification before container rollout (systemic gap) 2. The v2.4.1 migration added a NOT NULL column without a default value (triggering condition) 3. Existing rows failed the constraint check, causing 502 errors on
/accountsfrom 14:32–15:07 UTC (impact)Action Item #1: Add a pre-deploy step that runs
migrate --dry-runagainst a production snapshot and blocks deployment if any constraint violation affects >0 rows. Owner: Platform team. Due: Sprint 47. Verification: CI log shows dry-run step executing on next production deploy.
Prompt structure
The sections this prompt guides the model through.
- Summary
- Timeline
- Root Cause Chain
- What Went Well
- What Went Poorly
- Action Items
Opening lines
The first lines of the prompt itself.
Generate a blameless incident postmortem from the following incident notes.…
One rule from the prompt
A single rule — the full prompt contains more.
NEVER use phrases like "X failed to" or "Y should have." Describe what happened, not who failed. Write action items as engineering tasks, not behavioral changes — "add circuit breaker on service X," not "be more careful with deployments."
Unlock the full prompt
Part of the Engineering Toolkit Pack — 7 prompts for CHF 19.
View pack — CHF 19