Find and fix the cause of a reported bug, crash, regression, or intermittent failure. Use when symptoms are vague or reproduction is difficult. Rank hypotheses before inspecting code. Require a failing reproduction and evidence that the fix passes. Route design-level changes through the planning skills. Do not use for planned features, refactoring, or code-quality cleanup.
