trellis-break-loop

Perform a root-cause analysis by running a post-fix deep-dive to classify the bug category, identify why previous fixes failed, and generate concrete prevention mechanisms. This process outputs a structured, machine-readable summary suitable for indexing.

To stop the fix-forget-repeat debugging cycle, conduct a post-mortem analysis that categorizes root causes like Missing Spec or Test Coverage Gap, then captures the results into actionable specs and checklists to guide future development.

Post-mortem knowledge capture works by outputting actionable specs and checklists from the deep-dive analysis. It classifies bugs into categories such as Cross-Layer Contract or Implicit Assumption to inform teams across projects.

Yes, you can use post-mortem specs to prevent recurrence by prescribing concrete mechanisms including documentation updates, architecture improvements, enhanced tests, and process changes based on the identified root-cause category.

Root-cause categories identified during a post-fix deep-dive include Missing Spec, Cross-Layer Contract, Change Propagation Failure, Test Coverage Gap, and Implicit Assumption, each with specific prevention mechanisms.

You need to generate a preventive-specs package immediately after releasing a bug fix. Running this post-fix deep-dive analysis creates a root-cause category report that informs future development and validation.