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-mortem analysis after every bug fix and turning insights into permanent documentation. ## Core Features & Use Cases - Five-Dimension Analysis Framework: Classifies root cause (missing spec, cross-layer contract, change propagation failure, test coverage gap, implicit assumption), reviews why earlier fixes failed, and proposes prevention mechanisms. - Structured Output Template: Produces a standardized Markdown bug analysis report with prioritized prevention actions (P0, TODO/DONE status). - Knowledge Capture into Specs: Directs 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 Skill to classify it as an implicit-assumption bug, document prevention mechanisms, and update the cross-layer thinking guide. ## Quick Start After fixing a bug, ask the AI to run a break-the-loop deep analysis on the bug just fixed and update the relevant spec guides.
