ywc-incident-postmortem

Incident postmortem generation reconstructs the timeline, performs 5 Whys root cause analysis, and defines prevention action items to capture critical learnings after a production outage before memory fades.

Root cause analysis for a security incident is handled by dispatching security advisors automatically when auth bypass, data leaks, or OWASP vulnerabilities are detected, ensuring specialized investigation for the report.

Sanitized client-facing incident reports are generated automatically, providing professional external stakeholder communication while keeping internal technical details and root cause analysis private.

Generating incident postmortems requires the gh dependency for integration and benefits from incident context to accurately reconstruct the timeline and assess impact.

The 5 Whys technique is needed during incident documentation to systematically identify the underlying root cause of production outages or security incidents, ensuring actionable prevention steps are defined.

Automated postmortem generation relies on provided incident context to reconstruct timelines and define prevention action items, meaning incomplete input data will limit the accuracy of the root cause analysis.