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 a completed debugging session into a structured root-cause analysis so the knowledge is captured in specs instead of being forgotten. ## Core Features & Use Cases - Five-Dimension Analysis Framework: Classifies the root cause (missing spec, cross-layer contract, change propagation failure, test coverage gap, implicit assumption), reviews why earlier fixes failed, and defines prevention mechanisms. - Structured Output Template: Produces a standardized Markdown bug analysis report with prioritized prevention actions (P0/P1) and systematic expansion of similar risks. - Knowledge Capture into Specs: Directs immediate updates to .trellis/spec/guides/ thinking guides, syncs templates to src/templates/markdown/spec/, and commits the spec changes. - 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 prevention mechanism, 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.
