ワンクリックで
question-ladder
Use when uncertainty remains and the minimum useful sequence of questions should be asked.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when uncertainty remains and the minimum useful sequence of questions should be asked.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | question-ladder |
| description | 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.
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.
Agent Brain /brain-design: a product brief needs ux or interaction design before planning.
Agent Brain /brain-eval: changing Agent Brain behavior or checking quality.
Agent Brain /brain-grill: the idea, brief, design, or plan has unresolved assumptions.
Agent Brain /brain-learn: after repeated success/failure, a tricky fix, or a shipped workflow.