ask-questions-if-underspecified

Clarifying underspecified requirements involves asking 1-5 must-have questions to remove ambiguity before implementation. This ensures objectives, scope, and constraints are fully defined to prevent wasted effort and rework.

Requirements gathering is the process of defining objectives, scope, and constraints. Use clarifying questions when a request is underspecified and has multiple plausible interpretations, ensuring safe execution before action.

Prevent wasted effort by applying a pause before action on ambiguous requests. Use fast-path defaults to provide safe initial directions, reducing back-and-forth while keeping work scoped to essential details.

A prompting strategy for decision-making with incomplete information uses structured questioning to identify must-have details. It applies fast-path defaults when preferences are assumed, allowing safe progression despite missing constraints.

Yes, you can use fast-path defaults to skip extensive discovery for simple tasks. These defaults provide safe, initial directions when preferences are assumed, reducing back-and-forth while maintaining essential scoping.

The limitation of questioning for scope clarification is that it pauses work until answers are provided. If objectives or environment details remain unaddressed, the fast-path defaults may not fully capture complex constraints.