postmortem

To conduct a post-incident retrospective, run a guided workflow that traces escaped bugs to root causes by uncovering phase introduction, gate failures, and prevention plans through interactive Q&A. This structured approach ensures thorough incident context capture.

Root cause analysis for escaped bugs is a governance process that investigates why defects bypassed SDLC gates. It identifies phase introduction and gate failures to attach prevention rules, preventing recurrence by logging antipatterns for future development cycles.

To prevent incident recurrence, log antipatterns by creating an AP-NNN entry tied to specific incident references during your retrospective. This attaches prevention rules to a learning loop, ensuring the same escaped bugs are caught at failing gates going forward.

Yes, incident retrospective tracking works with .etc_sdlc files by storing structured YAML-based records. It integrates directly with incident and journal tracking for governance, ensuring changes commit to the antipatterns log and related incident references.

Yes, you can run a standalone root cause investigation outside of a live incident. The guided retrospective workflow is applicable during post-incident retrospectives or standalone investigations to trace escaped bugs and establish prevention rules.