postmortem

To create a post-mortem document, this skill guides you through timeline reconstruction, root cause analysis using the 5 Whys methodology, and action item generation to produce structured markdown documentation.

Root cause analysis works by guiding users through the 5 Whys methodology to identify systemic failures, shifting the incident response focus from assigning blame to implementing systemic process improvements.

Yes, you can automatically generate and track high-priority backlog items from the root cause analysis, converting incident data directly into Jira-style issues to prevent incident recurrence.

Yes, you need git history access because timeline reconstruction automatically gathers git logs and decision-log entries to build a chronological record of the incident within your software development lifecycle.

The best way to convert incident data into process improvements is using a structured framework that analyzes project state files and git history to generate actionable backlog items for long-term fixes.