What problem does it solve? After a bug or crash reaches production, teams often fix the symptom without understanding the systemic failures that allowed it. This Skill produces a rigorous post-mortem that traces both how the issue was introduced and how it escaped every quality gate, then converts findings into tracked prevention tasks. ## Core Features & Use Cases - Dual-Chain 5 Whys Analysis: Traces how the issue was introduced (Chain A) and how it escaped unit tests, integration tests, code review, CI, QA, staging, and monitoring (Chain B). - Structured Post-Mortem Document: Generates a complete markdown report with timeline, systemic root cause classification, impact, resolution, and recurrence checks, saved to docs/artifacts/post-mortem/. - Mandatory Prevention Tasks: Creates one Kanban board task per prevention action via the board adapter, with priority SLAs and recurrence escalation. - Use Case: After running /investigate-crash on a production NullPointerException, run this Skill to deepen the analysis, discover that DTO nullability was never validated against the API contract, and file P1 tasks to add a Konsist test and fix the mock data fixtures. ## Quick Start Ask the AI to write a 5 Whys post-mortem for the crash investigation you just completed, including prevention tasks on the board.
