What problem does it solve? Teams often fix a bug and move on, only to hit the same class of bug again later. This Skill performs a structured post-fix analysis that identifies the root cause category, explains why earlier fix attempts failed, and converts the findings into concrete prevention mechanisms and documentation updates. ## Core Features & Use Cases - Root Cause Classification: Categorizes each bug into one of five categories (missing spec, cross-layer contract, change propagation failure, test coverage gap, implicit assumption) with a structured Markdown output template. - Prevention Planning: Produces a prioritized table of prevention mechanisms spanning documentation, architecture, compile-time checks, runtime monitoring, test coverage, and code review. - Knowledge Capture: Directs immediate updates to .trellis/spec/guides/ thinking guides, syncs templates to src/templates/markdown/spec/, and commits the spec changes as the primary deliverable. - Use Case: After fixing a bug where an API returned timestamps in seconds instead of milliseconds, run this analysis to classify it as an implicit assumption bug, document the contract in the cross-layer thinking guide, and add a checklist item to prevent recurrence. ## Quick Start Ask the AI to run the break-loop analysis on the bug you just fixed and update the relevant spec guides with the findings.
