Incident Postmortem Report Generator

How It Works

After an incident, the last thing anyone wants to do is spend 3-5 hours

reconstructing what happened. This skill gathers the data trail and

produces a first draft: timeline, root cause analysis, contributing factors,

and action items.

What You Get

• Auto-generated incident timeline from deployment logs, alerts, and monitoring data
• Root cause analysis based on the evidence chain
• Contributing factors identification (process gaps, missing monitoring, documentation gaps)
• Action items categorized by priority and assignee
• Formatted in your team's postmortem template (Google SRE, PagerDuty, custom)
• Blameless language throughout

Setup Steps

1. After resolving an incident, point your Claw at the relevant data sources
2. Provide the incident time window and affected services
3. Review the draft, add human context (decisions made, communication gaps)
4. Share with the team for review

Tips

• The sooner after the incident you run this, the fresher the data
• It drafts blameless — if it catches itself blaming, it reframes
• Add your own observations about what was confusing or slow during response
• Use the action items as a starting point, then prioritize with the team
• Pairs naturally with Log Detective for deeper root cause analysis