When to use it
Run $status or /status when returning after a break, after a context clear, or whenever the next workflow action is unclear.
What it reads
- Build-plan completion
- Current feature, fix, or rollback checklist progress
- Project overview freshness
- Project configuration validity and configured branch prefixes
- Git branch and working-tree state
- Common Blueprint drift signals
Output
Status reports what is complete, what is active, what remains, and the exact recommended next command. It is intentionally operational and does not replace the product overview.
Status understands rollback/ branches and treats a rollback’s checked target as
valid until /complete unchecks it. It does not confuse that target with the next
unchecked feature.
When every planned item is checked, Status reports the current milestone as complete. It can suggest hardening, release, or docs, or point to /feature "new capability" to extend the same living build plan.
Read-only guarantee
Status does not modify plans, source code, branches, or commits. Use doctor when the question is whether Blueprint itself is installed and configured correctly.
Terminal status is separate
This page documents the project-local $status and /status agent skill. The
deterministic terminal CLI is separate and does not require an agent
conversation. See CLI Status for
npx create-ai-blueprint@latest status, the optional global blueprint status
command, JSON output, and target-directory behavior.