| name | systematic-debugging |
| description | Use when a bug, failure, or confusing behavior appears. Focus on root cause, not random edits. |
Systematic Debugging
Use this skill when something is broken and guessing would waste time.
Workflow
- Reproduce the problem clearly.
- Gather the smallest evidence that shows the failure.
- Form one root-cause hypothesis at a time.
- Test the hypothesis before editing.
- Fix the confirmed cause.
- Verify the original problem is gone.
Guardrails
- Do not stack multiple guesses together.
- Do not call it fixed without proof.
- Keep notes short and evidence-based.