incident-postmortem

Write blameless, high-impact incident reports

Transform chaotic production outages into structured engineering wisdom. This skill acts as a Senior SRE to help your team reconstruct timelines, identify systemic root causes, and define actionable improvements after any production incident, data loss event, or security breach.

What it does

• Reconstructs precise timelines: Consolidates raw data from Slack threads, PagerDuty alerts, logs, and metrics into a chronological event log.
• Deep Root Cause Analysis: Employs the "5 Whys" method to move past technical triggers and uncover underlying process or architectural gaps.
• Calculates Key Metrics: Automatically determines Time to Detect (TTD), Time to Mitigate (TTM), and total incident duration.
• Generates Concrete Action Items: Creates P0-P2 tasks with owners and due dates, specifically designed to prevent recurrence and reduce blast radius.

Why use this skill

Writing postmortems is often a manual, time-consuming chore that engineers avoid. This skill automates the heavy lifting of data synthesis while maintaining a strictly blameless culture. Unlike generic AI prompting, it follows industry-standard frameworks from Google and PagerDuty, ensuring your reports are professional enough for leadership and detailed enough for dev teams.

What the output looks like

You receive a professional, markdown-ready postmortem document containing a summary for stakeholders, a detailed event-source timeline, a quantified impact analysis, and a prioritized table of action items focused on systemic fixes rather than human error.