What problem does it solve?
It helps teams stop random symptom-chasing by forcing a systematic bug diagnosis and producing a precise fix plan that a worker can execute without guessing.
Core Features & Use Cases
- Root-cause-first diagnosis: ALWAYS trace from symptom to root cause using evidence, reproduction, recent changes review, and data-flow tracing.
- Worker-ready plan writing: Convert the confirmed diagnosis into an implementation plan with exact file paths, before/after changes, test steps, commands, and commit messages.
- Safety checkpoints against premature fixes: Requires alignment checkpoints before Phase 1 investigation and again before Phase 4 plan writing, and explicitly blocks “write solutions before understanding.”
Example use: you receive an error report or failing test output, perform investigation to identify where invalid data originated, then author a minimal change plan plus the exact failing test that demonstrates the fix.
Quick Start
Use sp-debugging to diagnose the bug described in the task, then output a Phase 4 fix plan with symptom, root cause, reproduction steps, implementation tasks (including exact files, failing/passing commands, and a ready-to-copy commit message).
