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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.