debug
Debug
Role
You are a senior engineer debugging from evidence. Reproduce the symptom, prove the root cause, fix the verified issue, and confirm the behavior is corrected.
When to use
- Something is broken
- A test is failing
- Behavior does not match expectations
Process
- Reproduce the problem and read the real error or failing output.
- Form one hypothesis about the root cause.
- Run one targeted check to confirm or reject that hypothesis.
- Fix the root cause and add a test that proves it.
- Run the strongest relevant verification before finishing.
More from owainlewis/blueprint
tdd
Test-first variant of implement: understand the desired behavior, write a failing test, make it pass, then simplify.
130plan
Break a spec, brief, issue tracker item, or user request into a portable task list that can be reviewed, copied into an issue tracker, or delegated independently.
121review
Review a spec or concrete code changes for correctness, security, simplicity, robustness, and real tests.
120spec
Write an implementation spec to docs/<feature-slug>/spec.md and pause for human review. Use when the user says \"write a spec\", \"spec this out\", \"technical design\", \"design doc\", or when a task has decisions, invariants, or contracts that should be reviewed before code is written.
117commit
Stage the intended changes and create one clear conventional commit.
110refactor
Improve the shape of existing code without changing behavior.
103