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 gap, implicit assumption), reviews why earlier fixes failed, and derives prevention mechanisms. - Structured Output Template: Produces a standardized Markdown bug analysis 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 cross-layer API format mismatch, run this analysis to classify the cause, add a contract checklist to the relevant thinking guide, and create a ticket for a type-safe wrapper. ## 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.