ask-questions-if-underspecified

To clarify underspecified requirements, you can describe your request and receive 1-5 targeted questions. This identifies unclear objectives, scope, constraints, environment, and safety details, halting progress until you provide essential answers to reduce rework.

Resolving unclear scope and objectives requires prompting focused questions to stakeholders. By guiding users through must-have questions before work begins, you reveal necessary constraints and environment details, enabling safe and incremental product management progress.

Ask 1-5 must-have questions when a workflow request is underspecified. This targeted approach ensures you focus only on resolving serious doubts about the objective, scope, constraints, and environment, avoiding overwhelming the stakeholder while ensuring safe progress.

You need to prompt clarifying questions when there are serious doubts about a request's objective, scope, constraints, environment, or safety. This is essential when requests are underspecified and you must reduce the risk of rework before implementation begins.

Yes, this approach halts progress until essential answers are provided. By delivering a concise set of must-have questions and stopping implementation, it ensures that scope is fully resolved and prevents moving forward with serious doubts about requirements.