Find the cause of bugs before changing code.
Guides bug investigations toward evidence-backed causes, minimal fixes, and targeted regression checks.
When to use it
Use when investigating bugs, regressions, failing tests, build or integration failures, flaky behavior, performance anomalies, or other unexpected technical behavior.
It changes how the agent investigates and fixes project failures by requiring sufficient root-cause evidence before a causal fix.
What you provide
Bug and failure requests must enter through scope-triage before the root-cause investigation.
For behavior bugs with an automated seam, requires tdd to establish a failing regression test before production changes and own GREEN and REFACTOR.
Requires handing successful debugging evidence to verification-gate for authoritative final verification and completion claims.
Routes browser evidence collection to web-debug when needed; browser capability is unnecessary when static inspection or tests localize the issue.
No additional actions listed.