What problem does it solve? When testing surfaces something unexpected, teams often guess at the fix and either patch the wrong thing or stall the entire build. This Skill classifies each discovery as a bug, missing requirement, or regression, determines its scope, and routes it to the correct response without derailing work in flight. ## Core Features & Use Cases - Three-way classification: Distinguishes bugs (spec exists, code doesn't follow it), missing requirements (behavior never defined), and regressions (previously Done work now broken) before any action is taken. - Scope-based routing: Routes each finding by blast radius — current slice, Done slice, unbuilt slice, adjacent slices, or flow-level — with a specific action table for each combination, including targeted-fix versus full-rebuild assessment for reopened slices. - Decision logging: Records every triage outcome in docs/backlog.md with type, scope, classification rationale, and action taken so future sessions don't relitigate past decisions. - Use Case: During QA sign-off, a user notices an empty state with no defined behavior. The Skill classifies it as a missing requirement, scopes it to the current slice, defines the behavior, adds it to the done criteria, and logs the decision — all without pausing the build. ## Quick Start Ask the assistant to triage an unexpected finding from testing, describing what was found and where it appeared, so it can classify the issue and route it to the right fix path.
