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
- Independent-review request, receipt, reviewer selection, and freshness
- 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.
Before suggesting new work, Status checks for interrupted completion. A matching
archive, branch, or unfinished closeout routes to /complete for full recovery
checks. Conflicting evidence needs repair first; a reset spec alone does not
prove completion. Settled history on a clean default branch does not prevent
starting the next feature.
Overview freshness uses the same checkbox-normalized plan fingerprint as the terminal status command and dashboard. Checking off completed work does not make the overview stale. Status recommends Overview only when plan content changed, the overview is missing, or its fingerprint cannot be verified. It does not use file modification times for this decision.
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.
Status also reads git.landing. In the default local-merge workflow, an active
feature that differs from the next unchecked build-plan item remains a drift
warning. Pull-request landing permits that order because another isolated
checkout may already be handling the earlier 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.