Clarify Requirements
Use this skill when the request is underspecified, high-risk, product-heavy, or likely to be misimplemented without more context.
Native Integration
Use the active agent's native chat, Ask/read-only mode, question tool, or planning surface to gather context. This skill only defines which questions are worth asking and what a usable brief must contain.
Workflow
Ground first.
- Read relevant repo files, docs, tests, issue text, current branch, and git status.
- Do not ask questions that local context can answer.
State the current understanding.
- Summarize the goal in one or two sentences.
- Call out known constraints and likely success criteria.
- Separate facts from assumptions.
Ask only decision-changing questions.
- Ask about scope boundaries, user-visible behavior, compatibility, data contracts, rollout, risk, and acceptance criteria.
- Prefer one question at a time when the answer changes the next question.
- Include a recommended answer when there is a sensible default.
Resolve ambiguity into a usable brief.
- Capture the final goal, in-scope work, out-of-scope work, constraints, assumptions, and acceptance criteria.
- If the work is now implementable, hand off to
plan-implementation or tdd-vertical-slice.
Done When
- The agent can explain what must change and what must not change.
- The user-visible success criteria are explicit.
- Major trade-offs have a chosen direction or a documented assumption.
- No remaining question would materially change the implementation plan.
1---2name: clarify-requirements-23description: Interview the user until goal, scope, constraints, success criteria, and trade-offs are clear enough to plan or implement.4---56# Clarify Requirements78Use this skill when the request is underspecified, high-risk, product-heavy, or likely to be misimplemented without more context.910## Native Integration1112Use the active agent's native chat, Ask/read-only mode, question tool, or planning surface to gather context. This skill only defines which questions are worth asking and what a usable brief must contain.1314## Workflow15161. **Ground first.**17 - Read relevant repo files, docs, tests, issue text, current branch, and git status.18 - Do not ask questions that local context can answer.19202. **State the current understanding.**21 - Summarize the goal in one or two sentences.22 - Call out known constraints and likely success criteria.23 - Separate facts from assumptions.24253. **Ask only decision-changing questions.**26 - Ask about scope boundaries, user-visible behavior, compatibility, data contracts, rollout, risk, and acceptance criteria.27 - Prefer one question at a time when the answer changes the next question.28 - Include a recommended answer when there is a sensible default.29304. **Resolve ambiguity into a usable brief.**31 - Capture the final goal, in-scope work, out-of-scope work, constraints, assumptions, and acceptance criteria.32 - If the work is now implementable, hand off to `plan-implementation` or `tdd-vertical-slice`.3334## Done When3536- The agent can explain what must change and what must not change.37- The user-visible success criteria are explicit.38- Major trade-offs have a chosen direction or a documented assumption.39- No remaining question would materially change the implementation plan.
santos-sanz