charlieviettq Clarify underspecified requests
When to use
- Multiple plausible interpretations exist.
- Objective, scope, constraints, or "done" criteria are missing.
- Quick read-only discovery cannot resolve the ambiguity.
When not to use
- Request is already specific enough to proceed.
- A short repo/config read answers the open questions.
Workflow
- Decide if the request is underspecified (objective, scope, constraints, environment, safety).
- Ask 1-5 questions max; prefer multiple-choice with a
defaultsfast path. - Separate need to know vs nice to know.
- Do not run mutating commands or commit to a detailed plan until must-have answers arrive.
- If the user asks to proceed without answers, state assumptions explicitly and get confirmation.
Question format
1) Scope?
a) Minimal change (default)
b) Broader refactor in the same area
c) Not sure - use default
Reply: defaults (or 1a 2b)
Anti-patterns
- Do not ask what a quick read of repo/docs already answers.
- Do not ask open-ended questions when a yes/no or A/B choice is faster.
Output
Restate requirements in 1-3 sentences (constraints + success criteria), then start work.