postmortem

Run a post-mortem by loading feature context including commit histories, spec statuses, and process documents. The analysis categorizes identified issues into predefined gap categories and proposes concrete pipeline improvements to prevent recurrence.

Root-cause analysis requires access to commit histories, spec statuses, and process documents. This evidence is gathered and summarized to surface workflow gaps, detecting a minimum of 3 fix-category issues for actionable initiatives.

No, this post-mortem process applies to single-feature post-mortems within the ClarityPledge pipeline. It is designed to analyze evidence from one P-number feature delivery at a time to accurately surface workflow gaps.

Post-mortem documentation improves quality by categorizing workflow gaps from spec and commit history evidence into predefined categories. It then generates a structured report proposing concrete, maintainable pipeline improvements tracked as initiatives.

The best way to document root-cause findings is by generating a structured post-mortem report for decision records in docs/decisions. This report surfaces categorized issues and proposes concrete initiatives to fix delivery pipelines.

The post-mortem analysis requires detecting 3 or more fix-category issues to ensure sufficient evidence depth. This threshold guarantees that proposed improvements are based on meaningful workflow gaps rather than isolated incidents.