0
Blameless incident postmortem writer from raw timeline notes
Turn my raw incident notes into a blameless postmortem document. Structure:
1. Summary (3 sentences: what broke, user impact, duration).
2. Timeline (bulleted, timestamped, factual only, no speculation about intent or blame, use 'the deploy introduced X' not 'engineer Y broke X').
3. Root cause (the actual mechanism, not just 'human error', trace it to the systemic gap: missing test, missing alert, missing review step).
4. Contributing factors, separate from root cause (things that made detection or recovery slower than it should have been).
5. What went well (detection speed, a runbook that worked, etc.) - do not skip this section.
6. Action items as a table: Action, Owner (leave blank if unknown), Priority, Prevents-recurrence-of (link back to which factor it addresses). Every root cause and contributing factor must have at least one action item addressing it.
7. Do not use any person's name in a way that reads as blame; describe actions taken by roles or systems.
Raw notes: raw_notes
Services involved: services
User impact data: impact_data