Dev Incident Postmortem Template
================================

Create an incident postmortem document for [incident description].

Incident details:
- Date: [date]
- Duration: [start to resolution]
- Severity: [P1/P2/P3]
- Impact: [users affected/revenue impact/SLA breach]
- Systems affected: [list]
- On-call responders: [roles]

INCIDENT POSTMORTEM

INCIDENT SUMMARY
- What happened: [1-2 sentence summary]
- Impact: [quantified — X users affected for Y hours]
- Root cause: [one sentence]
- Contributing factors: [list]
- Status: [resolved]

TIMELINE
| Time | Event |
| [HH:MM] | [First signs of issue] |
| [HH:MM] | [Alert fired / User reported] |
| [HH:MM] | [On-call paged] |
| [HH:MM] | [Initial investigation begins] |
| [HH:MM] | [Root cause identified] |
| [HH:MM] | [Fix deployed] |
| [HH:MM] | [Issue confirmed resolved] |
| [HH:MM] | [All-clear communicated] |

ROOT CAUSE ANALYSIS

5 WHYS
Why 1: [immediate cause]
Why 2: [cause of why 1]
Why 3: [cause of why 2]
Why 4: [cause of why 3]
Why 5: [root cause]

CONTRIBUTING FACTORS
- [Factor 1]: [how it contributed]
- [Factor 2]: [how it contributed]

WHAT WENT WELL
- [Detection was fast because...]
- [Communication was effective because...]
- [Rollback worked because...]

WHAT WENT POORLY
- [Monitoring did not catch X because...]
- [Runbook was outdated]
- [Took X minutes too long to identify because...]

ACTION ITEMS
| Action | Owner | Priority | Due Date | Status |
| Add alert for [metric] | [team] | P1 | [date] | Open |
| Update runbook for [scenario] | [team] | P2 | [date] | Open |
| Add test for [edge case] | [team] | P2 | [date] | Open |
| Review [process] | [team] | P3 | [date] | Open |

METRICS
- Time to detect: [minutes]
- Time to acknowledge: [minutes]
- Time to resolve: [minutes]
- Total downtime: [minutes]
- Users impacted: [number]

NO BLAME POLICY
This document focuses on systems and processes — not individuals.
All team members acted in good faith with the information available.

Source: https://promptzyo.com/prompt/dev-incident-postmortem-template