ask-questions-if-underspecified

Clarifying underspecified requests requires asking must-have questions across objectives, scope, constraints, environment, and safety before acting, ensuring accurate interpretation and preventing wasted implementation effort.

Handling underspecified requests involves using a pause-before-acting workflow that prompts essential questions first, confirming interpretation before proceeding to reduce misinterpretations and mitigate risk in decision-making.

Yes, you can use structured question templates to manage risk by systematically identifying gaps in objectives, scope, constraints, environment, and safety, forcing a pause before implementation until requirements are specified.

When objectives and scope are underspecified, you should ask must-have questions covering constraints, environment, and safety, pausing all implementation actions until the user provides sufficient clarification.

A pause-before-acting workflow prevents misinterpretations by stopping premature implementation, prompting the user with essential question templates, and confirming interpretation before proceeding with the actual work.