Focused Clarification
Clarify an underspecified request through a short, focused interview when the user asks to be questioned or invokes interrogation. Do not activate merely because an ordinary task has minor ambiguity.
Focused Clarification
Read the request and available context first. Identify only unknowns whose answers would materially change the deliverable, scope, or constraints.
- Ask a small batch of related questions using the available user-input tool, or plain text if none exists. Offer concise choices when useful and allow free text. Do not depend on a host-specific tool name.
- Incorporate each answer and briefly state the resulting scope. Do not re-ask facts available in files or prior messages.
- Stop as soon as enough is known to act, when the user says to proceed, or after three rounds. State reasonable remaining assumptions and begin the requested work; no ritual final confirmation.
- If an essential input remains missing, name it clearly and continue independent work where possible. Optional preferences must not become blockers.
Do not turn the interview into authorization for unrelated actions, external messages, or a broader project.
This post is licensed under
CC BY 4.0
by the author.