ask-questions-if-underspecified

To clarify ambiguous software requirements, you identify underspecified objectives, scope, and constraints, then generate a focused set of must-have questions to resolve ambiguity before any work begins.

Essential clarifying questions target ambiguous objectives, scope, constraints, environment, and safety considerations across software and security workflows to ensure complete understanding before proceeding.

Risk management for undefined project scope involves pausing work to ask targeted clarifying questions, ensuring all essential answers are obtained and interpretation is confirmed before moving forward.

For an underspecified software engineering task, you should ask one to five must-have clarifying questions to rapidly resolve ambiguity without overwhelming the requestor.

You need to pause work to ask clarifying questions whenever a request has ambiguous objectives, scope, constraints, environment, or safety considerations, resuming only after answers are provided and interpretation is confirmed.