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 turns every completed debugging session into a structured root-cause analysis so the knowledge is captured in specs instead of being lost. ## Core Features & Use Cases - Five-Dimension Analysis Framework: Classifies the root cause (missing spec, cross-layer contract, change propagation, test coverage gap, implicit assumption), reviews why earlier fixes failed, and defines prevention mechanisms. - Systematic Expansion: Identifies similar issues elsewhere in the codebase, design flaws, and process improvements revealed by the bug. - Knowledge Capture into Specs: Updates .trellis/spec/guides/ thinking guides, syncs templates to src/templates/markdown/spec/, and commits the spec changes as the primary output. - 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, add a type-safe wrapper as prevention, and update the cross-layer thinking guide. ## Quick Start After fixing a bug, ask the AI to run the break-loop analysis on the bug just fixed and update the relevant spec guides.
