ask-questions-if-underspecified

To clarify ambiguous requirements before implementation, you can use a must-have-question workflow that prompts 1-5 essential questions to surface ambiguity and pauses execution until interpretations are confirmed.

Preventing wrong work from underspecified product design requests involves eliciting essential clarifying questions using a structured decision flow, ensuring objectives and scope are confirmed before concrete work begins.

The clarifying question workflow handles unclear project constraints by using a formal question tool with multiple-choice options to prune interpretations quickly, then pausing for user confirmation of the correct interpretation.

Yes, you can use this requirement clarification process for research planning, as it is applicable across domains where objectives, scope, or safety concerns are initially unclear and require structured elicitation.

You should ask 1-5 must-have questions to resolve underspecified requests, which provides a minimal set to surface core ambiguity at the outset without overwhelming the user before proceeding.

You should not use a must-have-question workflow when your project objectives, scope, and constraints are already fully specified and unambiguous, as the structured questioning process would introduce unnecessary delays.