ask-questions-if-underspecified

Clarifying underspecified requirements involves evaluating objective, scope, constraints, environment, and safety to identify ambiguity. You then generate 1-5 must-have clarifying questions in the first pass to minimize ambiguity and prevent premature commitments before proceeding with implementation.

Use a clarification workflow for ambiguous project requests when multiple plausible interpretations exist across objective, scope, constraints, environment, or safety. It applies a pause-before-acting mechanism to ensure decisions are validated and user-approved assumptions are established before execution.

The best way to identify ambiguous objectives and scope in decision-making is to apply a fast-path discovery step that evaluates the request for multiple plausible interpretations. This process prompts for must-have clarifying questions and provides clear defaults to prevent premature commitments.

During the requirements discovery phase, you should ask a minimum set of 1-5 must-have clarifying questions in the first pass. This concise set minimizes ambiguity while preventing premature commitments before proceeding with the requested work.

Yes, this requirements discovery approach provides clear defaults and a fast-path discovery step for unspecified constraints. It ensures decisions are validated through a pause-before-acting workflow, guiding user approval of assumptions before execution to prevent premature commitments.