ask-questions-if-underspecified

Resolve vague requests by asking targeted questions about scope, constraints, and acceptance criteria to fill information gaps. Identifying ambiguities and suggesting default options helps expedite decision-making and prevent misinterpretation before implementation begins.

Requirement scoping is the process of identifying ambiguities and resolving vague requests by defining scope, acceptance criteria, and constraints. It ensures clarity before implementation to prevent incorrect work and wasted development time.

Handle underspecified requests by asking focused questions about specific details like authentication methods, user roles, and design preferences. This ensures all necessary details are clarified and ambiguities are resolved before coding begins.

Unclear scope leads to wasted development time because ambiguous and multi-interpretable requests cause incorrect work. Clarifying underspecified requirements beforehand prevents misinterpretation by ensuring all necessary details are defined before coding begins.

Ask clarifying questions when requirements are underspecified, vague, or lack clear scope, constraints, and acceptance criteria. Identifying these ambiguities before implementation prevents incorrect work and wasted development time.