Command Guide - AI Blueprint Docs

Start with the task you have, then choose the command. All commands below run in your AI chat. Terminal commands such as npx create-ai-blueprint status manage the installed Blueprint; they do not invoke an AI skill.

Pick a starting point

I want to…	Use
Think through an idea or tradeoff	`/explore`
Understand a feature already in the build plan	`/brief`
Write the next feature spec	`/feature`
Diagnose something broken	`/debug`
Spec a known bug or small unplanned change	`/fix`
Verify the running product	`/check`
Get steps I can follow myself	`/check guide`
Review the code for defects and risks	`/audit current`
Set up repeatable unit tests	`/tests`
Set up repeatable browser tests	`/tests browser`
Check Blueprint installation and context	`/doctor`

Everyday build path

/feature -> /implement -> /check -> /audit current -> /complete

Review and approve the spec before implementation. This path explains the jobs involved; it does not change configured quality gates or require a separate manual audit on every feature. See Project configuration for automatic gate selection.

/check executes verification against the current spec. /check guide only explains what a person should run, click, and expect. /audit current reviews the code and records findings. A guide is not evidence that verification passed.

Build

Command	Job
/feature	Turn a planned item into a buildable spec.
/implement	Build the approved spec.
/check	Verify behavior; use `guide` for read-only manual steps.
/complete	Run final gates, archive work, and merge with approval.

Understand and review

Command	Job
/explore	Discuss ideas and inspect relevant code without changing files.
/brief	Explain an upcoming build-plan item before writing its spec.
/status	Show progress, drift, and the next action.
/debug	Reproduce and isolate a failure without fixing it.
/audit	Review code across concerns or with a focused lens.
/doctor	Check Blueprint setup and workflow health.

Plan and setup

Command	Job
/onboard	Tune Blueprint for a fresh scaffold.
/adopt	Introduce Blueprint into an existing app.
/discovery	Develop project plans through a guided conversation.
/overview	Distill the plans into durable project context.
/prototype	Create throwaway visual mockups.
/tests	Set up unit tests by default, or browser tests with `browser`.
/ci	Define one Verify command and matching GitHub checks.

Recover and release

Command	Job
/fix	Spec a bug fix or small unplanned change.
/rollback	Plan a history-preserving reversal.
/release	Prepare deployment configuration and readiness checks.

Automation

Command	Job
/autopilot	Run one explicitly requested bounded spec and implementation pass.
/continuous	Complete remaining planned features serially within configured limits.

Invocation and migration

Claude Code uses /explore, /tests browser, and /check guide. Codex uses $explore, $tests browser, and $check guide. Other supported tools can follow the matching skill through a natural-language request.

/browser-tests is now /tests browser. /try is now /check guide. /brief remains available for planned-feature briefings. See updating Blueprint for managed-file migration and preserved project guidance.