Incident postmortem draft
Auto-draft the postmortem from the incident channel — timeline, contributing factors, action items.
Eluu — incident-postmortem-draft
Shown in preview 
Runtime ~2m per run
Tokens ~14K per run
Owner an incident commander
Works with
Pick whichever tool your team already uses.
- Messaging Slack
Teams - Docs Notion
Google Docs 
Confluence - On-call PagerDuty
Opsgenie 
incident.io
What it does
Drafts a starter postmortem from the incident channel and on-call data so the IC isn’t starting from a blank doc. Reconstructs the timeline, pulls the alert chain, identifies contributing factors, and proposes action items with owners.
How it works
- Trigger. 24 hours after an incident resolves, the colleague picks up the resolved page.
- Pull channel. Reconstruct the timeline from
#incident-<id>messages. - Extract. Augment with the alert payload + responder timing.
- Draft. Compose summary + timeline table + contributing factors + action items in Notion.
Setup
- Connect an on-call tool (PagerDuty, Opsgenie, or incident.Io).
- Connect Slack with access to incident channels.
- Connect a docs tool (Notion, Google Docs, or Confluence).
Variations
- Run only for SEV-1 incidents.
- Auto-create Linear/Jira tickets from action items.
- Append a “blast radius” estimate based on user-impact telemetry.
