ask-questions-if-underspecified

To clarify underspecified requirements, you must identify unclear objectives, scopes, or constraints and generate targeted clarifying questions. This ensures must-have questions are asked first, pausing execution until answers are provided before proceeding.

You should ask clarifying questions during requirements gathering whenever the objective, scope, or constraints of an automation or coding task are unclear. This prevents wrong work by ensuring assumptions are restated and aligned with repo governance before execution.

The best way to avoid wrong work when given an unclear project scope is to ask the minimum must-have questions required to clarify the request. Restate assumptions and constraints, pausing execution until the user provides necessary answers.

No, this requirements clarification process does not trigger automatically. It must be invoked explicitly only when needed to identify underspecified requests, generate targeted questions, and pause execution for necessary answers.

To align assumptions with repository governance before proceeding, restate your assumptions and constraints after gathering necessary answers. This ensures the clarified requirements match governance rules before taking any further action on the task.