incident review writer

The problem

Engineering teams spend hours manually parsing Slack threads and logs to write incident reports. These reports often lack systemic depth, contain finger-pointing, or fail to produce verifiable action items.

What it does

• Converts raw Slack exports and alert logs into a structured, minute-by-minute incident timeline.
• Performs a 5-Whys root cause analysis focused on systemic failures rather than individual errors.
• Generates full, blameless postmortems ready for Confluence or Notion.
• Audits action items to ensure they are specific, verifiable, and have assigned owners and deadlines.

Why this beats prompting it yourself

Generic prompts often invent missing data or use accusatory language that damages team culture. This skill enforces strict blamelessness and explicitly separates proven facts from assumptions, ensuring your reports meet senior leadership standards without manual editing.

Use cases

• Turning a chaotic SEV-1 Slack war room thread into a professional postmortem.
• Gap analysis of incident evidence to identify where logs or monitoring are missing.
• Standardizing action items across multiple engineering squads to ensure accountability.

Known limitations

Requires raw text evidence (logs, chats, alerts) to function. Cannot independently verify external financial impact data unless provided by the user.