trellis-break-loop

What problem does it solve?

It helps teams stop the fix-forget-repeat cycle by performing deep, structured analysis after a bug is resolved so the real root cause and prevention strategy are captured into the repository.

Core Features & Use Cases

• Root cause categorization (A–E): Classifies the bug into missing spec, cross-layer contract failure, change propagation failure, test coverage gap, or implicit assumption to target the correct remediation.
• Failure mode review: Explains why earlier fixes did not stick (surface fix, incomplete scope, tool limitation, or mental model mismatch) when multiple attempts were required.
• Prevention mechanism design: Converts insights into durable defenses such as documentation updates, architectural constraints, compile-time/runtime safeguards, stronger tests, and review checklists.
• Knowledge capture into Trellis artifacts: Produces concrete next steps to update .trellis/spec/ guides/docs and create tickets for follow-through.

Quick Start

After you finish fixing a bug, run the trellis-break-loop workflow and analyze the root cause, why prior fixes failed (if any), and the specific spec/test/review updates needed to prevent the same class of bugs.