ask-questions-if-underspecified

To clarify ambiguous project requirements, you can generate a focused set of 1-5 must-have questions to disambiguate objective, scope, and constraints. This pauses implementation until answers are provided or assumptions are explicitly approved.

The best way to stop work on underspecified requests is using a pause-before-action guardrail that detects missing objective, scope, or safety details, holding all implementation until must-have questions are answered.

You should ask a minimum of 1 to 5 focused clarifying questions for an underspecified task. This concise set targets essential disambiguation to avoid wrong work without overwhelming the user.

You need to restate understood requirements during product management workflows immediately after receiving answers to your must-have questions, confirming your interpretation before you proceed to actual implementation.

Yes, you can proceed with a task if the user explicitly approves proceeding with stated assumptions. The workflow holds work until answers are provided or the user validates your assumptions.

A request is underspecified when it lacks sufficient objective, scope, constraints, environment, or safety details. Identifying these missing elements triggers the generation of must-have clarifying questions.