Use when the user needs a standup-ready summary of recent project activity from local evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use when uncertainty remains and the minimum useful sequence of questions should be asked.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Lifecycle stage: INTAKE
Use when missing answers block product, design, or engineering decisions.
Do not use when this trigger is absent; choose the command or skill that owns the requested state, artifact, and verification gate.
| Shortcut | Rebuttal |
|---|---|
| "This is obvious." | Write the assumption and evidence. If you cannot, it is not obvious. |
| "We can do this later." | If the missing step changes the decision, do it now or state the risk. |
| "The user wants speed." | Reduce scope; do not skip the quality bar. |
| "This does not need verification." | Every important claim or behavior needs proof. |
Open Questions plus assumptions
The artifact should be concise, auditable, and include evidence, blockers, and next action so another agent can resume.
Trigger: uncertainty remains after retrievable evidence has been checked. Action: ask the smallest useful next question or choose the safest documented default in noninteractive mode. Output artifact: intake or grill artifact with blockers and next action. Verification: cite evidence checked, why the question changes action, and stop condition if no answer is available.
A plan is blocked by "needs approval." The ladder should ask the smallest next question first: what side effect is approval-gated, what safe read-only alternative exists, what assumption can unblock planning, and what evidence would change the route.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when the user needs a standup-ready summary of recent project activity from local evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a command, adapter, or runtime smoke depends on proving an agent runtime's capabilities before trusting command routing, writes, shell access, or validation claims.
日本語の概要は準備中です。原文の説明を表示しています。
Use when agent-produced work needs a safety, evidence, and reliability check before handoff, merge, or trust.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an output artifact, template, schema, example, or handoff field must stay aligned across commands, skills, docs, and validators.
日本語の概要は準備中です。原文の説明を表示しています。
Agent Brain /brain-brief: after intake, research, and grill have enough signal.
日本語の概要は準備中です。原文の説明を表示しています。
Agent Brain /brain-build: an implementation plan has a selected task and validation method.
日本語の概要は準備中です。原文の説明を表示しています。