ask-questions-if-underspecified

To clarify underspecified requirements, you need to ask 1–5 concise must-have questions up front. This resolves ambiguity without over-constraining the task, pausing action until explicit confirmation is received to prevent wrong work.

Handling ambiguous requests involves pausing before acting and gathering essential clarifying questions first. By prompting for the minimum must-have answers, you prevent scope creep and ensure the workflow proceeds only after explicit confirmation.

Asking clarifying questions prevents scope creep by resolving multiple plausible interpretations before work begins. It pauses the workflow until must-have answers arrive, ensuring the team acts only on explicitly confirmed requirements.

Yes, you can use sensible defaults to proceed through a compact decision path. The workflow provides a fast-path response to maintain momentum, but still pauses to gather must-have answers before fully executing the task.

You need to pause a workflow for explicit confirmation whenever requirements are ambiguous or multiple plausible interpretations exist. Pausing gathers the minimum must-have questions first, ensuring the task proceeds only after explicit confirmation.