debug

<!-- rig-generated --> # debug+ — Systematic Debugging with Scout Context Wraps `superpowers:systematic-debugging`. Requires superpowers to be installed. No phase prerequisite — invoke from any skill chain phase when you encounter a bug, test failure, or unexpected behavior. ## Before You Begin This skill adds scout-mandated context harvesting on top of the base debugging skill: 1. **Scout context** — always map the affected code area via the scout agent before debugging 2. **Environment awareness** — detects test infrastructure, dependencies, and recent changes 3. **Constitutional awareness** — loads active enforcement rules from session context ## Procedure ### Phase A: Harvest Context 1. Reproduce the issue — run the failing command or test and capture the exact output. 2. Invoke the scout agent to map the affected area: ``` Agent(subagent_type="scout", prompt="Map the codebase around [affected files/modules]. Focus on: related functions, callers, test files, and recent changes.") ``` 3. Identify: - The exact failure symptom (error message, wrong output, crash) - The code path that produces the symptom - Recent changes that may have introduced the issue - Related test coverage - Active enforcement rules from session context (see session-start output) ### Phase B: Investigate (delegate to superpowers:systematic-debugging) 1. Invoke `superpowers:systematic-debugging` with the gathered context. 2. Follow the systematic debugging process:...