When to use it
Run $debug or /debug when you know something is failing but do not yet know why. Give it the failing command, error, or observed behavior when possible.
/debug "npm test fails in auth.test.ts"
/debug "saving a profile returns 500"The command is included in create-ai-blueprint@0.7.0 and later releases.
What it does
Debug gathers evidence with the smallest safe reproduction it can run, follows the failure through nearby code and configuration, and reports one of three verdicts:
- Confirmed: the evidence identifies the cause.
- Likely: the evidence points to a cause but cannot fully prove it.
- Blocked: a missing service, credential, environment, or reproduction step prevents a trustworthy diagnosis.
The report separates the visible symptom from the underlying cause and names the next workflow step.
Read-only boundary
Debug does not edit source, tests, configuration, lockfiles, Blueprint state, branches, or commits. If a diagnostic command changes the working tree, it stops and reports the change instead of cleaning it up.
What comes next
If the failure belongs to the active feature, fix, or rollback, continue with /implement. If it is a confirmed standalone bug and no work item is active, use /fix to write a focused spec before changing code.