Write a Postmortem
Write a Postmortem
ClaudeChatGPTGemini
Health
0/100
▲ 38
📋 119 copies
Trigger Phrase
Write a postmortem for
Prompt
96 wordsWrite a blameless postmortem for the following incident.
Incident summary: [PASTE YOUR INCIDENT TIMELINE AND NOTES]
Structure the postmortem as:
1. **Summary** (3 sentences: what happened, impact, duration)
2. **Timeline** (bullet points, times relative to detection: T+0, T+5min etc)
3. **Root Cause** (be specific — not 'human error' but the actual technical or process cause)
4. **Contributing Factors** (what made this worse or harder to detect)
5. **What Went Well** (what limited the blast radius)
6. **Action Items** (each must have: what, who owns it, by when)
Blameless means: focus on systems and processes, not individuals. Use 'the deployment script' not 'John's script'.
Incident summary: [PASTE YOUR INCIDENT TIMELINE AND NOTES]
Structure the postmortem as:
1. **Summary** (3 sentences: what happened, impact, duration)
2. **Timeline** (bullet points, times relative to detection: T+0, T+5min etc)
3. **Root Cause** (be specific — not 'human error' but the actual technical or process cause)
4. **Contributing Factors** (what made this worse or harder to detect)
5. **What Went Well** (what limited the blast radius)
6. **Action Items** (each must have: what, who owns it, by when)
Blameless means: focus on systems and processes, not individuals. Use 'the deployment script' not 'John's script'.
Install Instructions
Paste this prompt then your incident notes. Works best when you give a real timeline, even rough notes.
Test It
Test command:
Give it a fake incident: 'database went read-only for 40 minutes, caused by disk full on primary'
Expected output:
Should produce all 6 sections with specific, non-generic content
Pass criteria:
- All 6 sections present. Root cause is specific. Action items have owners and dates.
⚠️ Guardrails
- Review with your team before publishing — AI may mischaracterise events.