Explore an idea against the actual codebase without changing files. Investigate whether a change would help, compare alternatives and tradeoffs, and discuss uncertainty before deciding whether to plan anything. Use for /explore, considering an idea, or weighing options without writing a spec.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
Explore is a read-only conversation grounded in the actual project. It can help with questions such as whether caching would help a dashboard, whether teams belong in the product, or which upload approach fits existing code.
No plans or active feature are required. Do not require /overview, invent a
plan, or treat missing Blueprint context as a blocker to discussing the idea.
This command never writes activity state, including blueprint/.state/run.json.
Use the supplied topic or relevant conversation context. With neither, ask what the user wants to investigate. For a vague idea, state a tentative interpretation and ask a focused question only when its answer changes the investigation.
Reuse context already loaded in the session. Read relevant project instructions, code, tests as text, manifests, and existing plans when they help answer the question. Follow the actual implementation far enough to support your claims; point to concrete files or symbols. Avoid scanning unrelated parts of the repo. Read-only Git inspection can establish what exists or is already in progress.
Authoritative documentation lookup is appropriate when technical uncertainty needs it. Distinguish documented facts from what this project actually uses. Missing code or evidence is an uncertainty to explain, not permission to execute an experiment or to invent current behavior.
Keep the conversation proportional to the question. Compare plausible options against the user's needs and existing project constraints. Include doing nothing when the current behavior may already be sufficient. Do not invent scale, security requirements, or new abstractions to justify a change.
Explain the strongest case against your recommendation and how confident you are. Separate observed facts, assumptions, and unanswered questions. Say what evidence could change the recommendation without gathering it through execution. An unresolved question or a recommendation to leave the project alone is a valid outcome.
Use a small diagram in the response when it makes a relationship or tradeoff clearer. Do not create diagram files. There is no mandatory output template, report, question count, or next-step checklist. Follow the user's responses and let the discussion continue as long as useful.
/brief explains an existing build-plan item, its scope, dependencies, and
size. Explore can discuss an unplanned idea or question a planned approach./discovery develops broader product direction and reviewed planning drafts.
Explore does not draft either planning file./debug reproduces and isolates an actual failure. Explore discusses options
without executing code to diagnose or verify them./feature writes a buildable spec; /fix specifies a confirmed small change.
Suggest the appropriate command only when the user is ready to proceed.Do not force a handoff at the end of every response. Keep discussing the idea when that is what the user wants, and leave the project unchanged.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。