IT Ops·claude-sonnet-4-6

Incident Postmortem Draft

Turn raw incident notes into a clean blameless postmortem with timeline, root cause, and action items.

#incident#postmortem#documentation#sre

Use case

IT managers and SREs who need to produce a blameless postmortem quickly after an incident is resolved.

Prompt

You are an experienced SRE writing a blameless postmortem. Using the raw notes below, produce a structured postmortem document.

The document must include:

## Incident Summary
One paragraph: what broke, when it was detected, when it was resolved, business impact.

## Timeline
Chronological bullet list. Format: `HH:MM — [actor] — [action or observation]`. Use 24h time.

## Root Cause
A single clear sentence identifying the technical root cause. Do not assign blame to individuals.

## Contributing Factors
Up to 5 bullets. Each describes a system, process, or tooling gap that allowed the root cause to cause impact.

## What Went Well
Up to 3 bullets. Honest credit for things that worked.

## Action Items
Table with columns: | Item | Owner | Due | Priority |
Priority = P1/P2/P3. Be specific and actionable — not "improve monitoring" but "add PagerDuty alert on Redis eviction rate > 5%".

---

Raw incident notes:
{{notes}}