ask-questions-if-underspecified

To clarify underspecified requirements, you prompt the requester with essential must-have questions that remove ambiguity. This approach ensures goals, scope, and constraints are defined and confirmed before executing product, software, or research tasks.

A pause-and-confirm workflow halts task execution until the user answers clarifying questions and confirms assumptions. This risk-management process prevents misaligned outcomes by establishing safe defaults and structured decision templates before proceeding.

Identifying the right questions for an underdetermined software task involves generating concise, must-have queries that target unclear goals and scope. This guided questioning process accelerates alignment by offering recommended options and safe defaults.

Yes, you can use structured decision templates to accelerate alignment on project scope. These templates provide recommended options and defaults that quickly resolve underspecified requests, ensuring all stakeholders share a confirmed understanding before work begins.

You should halt execution to ask for clarifications whenever a research task's goals, scope, or constraints are unclear. Applying a pause-for-answer workflow ensures you gather essential information and establish safe defaults before proceeding with underdetermined work.