Check the running app, CLI, or server against the active spec's done-when criteria and capture observable pass or fail evidence without editing source. Use /check to verify real feature behavior, or /check guide [latest|scope] for a read-only manual walkthrough: how to test manually, where to click, expected and incorrect results, or a human review path.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.
/check guide or $check guide: generate a read-only manual walkthrough.
Pass remaining arguments such as latest, a step, a path, route, or command
to reference/guide.md. Read and follow that reference only. Do not write
activity state, run checks or the app, edit files, update spec status, or
produce verification receipts./check or $check, optionally with a verification scope: verify observed
behavior against the spec. Follow verification startup below, then read and
follow reference/verify.md only.Load only the selected reference. Do not read both references preemptively.
Guide generation never satisfies a verification gate. The existing
qualityGates.regular.tryGuide and qualityGates.continuous.tryGuide keys now
select /check guide. manual, always, and when-user-facing retain their
existing behavior. when-testable asks guide mode to classify whether the work
has a safe, meaningful observation path and generate a compact ## Try it now
section only when one exists. The separate check gates continue to select
verification mode.
First action: Before project inspection, preflight, or any other tool call,
publish running to blueprint/.state/run.json using the dashboard activity
contract in AGENTS.md, with command check. This precedes reading the
verification reference. Guide mode must skip this startup entirely.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Adopt Blueprint into an existing brownfield codebase by surveying shipped behavior and generating plans, standards, commands, adapter choices, and visibility setup. Use for /adopt or requests to bootstrap Blueprint into an established app. Use onboard for a fresh scaffold.
The English summary is being prepared. Showing the original description.
Audit current changes, a path, or the full project for quality, security, performance, or test problems and record durable findings. Independent mode prepares or completes a fresh-reviewer checkpoint handoff. Use for /audit, independent review, security review, code quality review, dead code, duplication, or standards drift.
The English summary is being prepared. Showing the original description.
Run one explicit bounded Blueprint spec and implementation pass through configured quality gates, then stop before completion or external actions. Use only when the user directly invokes /autopilot, $autopilot, or asks for Autopilot.
The English summary is being prepared. Showing the original description.
Brief an upcoming build-plan feature without writing files. Explain scope, dependencies, affected areas, size, and likely splits for the next item or a named item. Use for /brief, feature previews, what comes next, or build-order decisions before /feature.
The English summary is being prepared. Showing the original description.
Set up or normalize one project Verify command and matching GitHub Actions checks while preserving existing CI, with an optional local pre-push hook. Use for /ci, GitHub Actions setup, pull-request checks, automatic checks, pre-push hooks, or aligning typecheck, test, and build verification.
The English summary is being prepared. Showing the original description.
Complete a finished feature, fix, or rollback by running final gates, archiving its spec, updating plans, creating the work commit, and requesting approval to land it locally or by pull request. Use for /complete or requests to finish, wrap up, merge, or close the current work item.
The English summary is being prepared. Showing the original description.