diagnoselisted

# /wipnote:diagnose General-purpose diagnostic skill for investigating bugs, errors, and unexpected behavior. ## Usage ``` /wipnote:diagnose <bug-id> # Investigate a specific bug /wipnote:diagnose <error or symptom> # Investigate an error or behavior /wipnote:diagnose --delegation # Audit delegation compliance (legacy mode) ``` ## When to Activate Trigger on: - "diagnose", "debug", "investigate", "root cause", "why is this broken" - A bug ID like `bug-5126e3cf` - An error message or symptom description - "why isn't X working", "what's wrong with", "figure out why" - "delegation audit", "delegation score" (routes to delegation mode) ## Work Item Attribution All diagnostic work must be attributed: - Bug investigation: `wipnote bug start <bug-id>` before investigating - New errors: `wipnote bug create "Error: description" --track <trk-id>` then start it - Run `wipnote help` for available commands ## Instructions for Claude ### Route by Input **If given a bug ID** (matches `bug-*`): 1. Start attribution: `wipnote bug start <bug-id>` 2. Fetch bug details: `wipnote bug show <bug-id>` 3. Dispatch the debugger agent with the bug context 4. Present findings and suggested fix **If given an error message or symptom**: 1. Create and start a bug: `wipnote bug create "<summary>" --track <trk-id>` then `wipnote bug start <id>` 2. Dispatch the debugger agent with the error context 3. Present findings and suggested fix **If `--delegation` flag**: 1. Run th