ask-questions-if-underspecified

Clarifying underspecified workflow requirements involves identifying missing details about objectives, scope, constraints, and acceptance criteria, then asking targeted questions to gather essential information before task execution to prevent wasted effort.

Preventing wasted effort from ambiguous task requests requires a structured approach to identify missing information and prompt for essential details using concise, multiple-choice questions with suggested defaults before proceeding with implementation.

Structuring questioning to gather missing acceptance criteria and scope requires identifying underspecified elements in the request and prompting the user with concise, multiple-choice questions that include suggested defaults to speed up the clarification process.

You need to ask clarifying questions for a software engineering task whenever ambiguity could lead to incorrect implementation or wasted effort, such as when a request to update a user profile page lacks details on fields or design constraints.

Yes, this requirement clarification approach applies to any underspecified user request where ambiguity could lead to incorrect implementation, ensuring all necessary information is gathered before starting the task to avoid assumptions and rework.