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 breaks the fix-forget-repeat cycle by guiding a structured post-fix analysis that identifies the root cause category, explains why earlier fix attempts failed, and converts the lessons into updated specs and prevention mechanisms. ## 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 failed fix attempts, defines prevention mechanisms, expands to systemic issues, and captures knowledge. - Structured Output Template: Produces a standardized Markdown bug analysis report with prioritized prevention actions (P0, TODO/DONE status). - Spec 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, add a compile-time type guard, and update the cross-layer thinking guide so the whole team avoids the same mistake. ## Quick Start Analyze the bug we just fixed using the break-loop framework and update the relevant thinking guides in the spec directory.
