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 forcing a structured post-fix analysis that captures root causes and converts them into durable documentation and prevention mechanisms. ## Core Features & Use Cases - Root Cause Classification: Categorizes bugs into five types (missing spec, cross-layer contract, change propagation failure, test coverage gap, implicit assumption) with a structured analysis template. - Prevention Planning: Maps each bug to concrete prevention mechanisms such as documentation, type-safe architecture, compile-time checks, runtime monitoring, and test coverage. - Knowledge Capture: Directs updates to .trellis/spec/guides/ thinking guides and syncs templates so insights persist beyond the chat session. - 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, identify similar risks across the codebase, and update the cross-layer thinking guide. ## Quick Start Analyze the bug I just fixed and update the relevant spec guides to prevent this class of bug from recurring.
