ask-questions-if-underspecified

To clarify underspecified requirements, prompt the requester for essential details like objective definitions, acceptance criteria, and scope. This prevents wrong work by pausing implementation until the user explicitly confirms assumptions or approves stated defaults.

Defining scope and acceptance criteria requires asking must-have questions about success objectives, constraints, environment requirements, and safety checks. Gathering these details upfront ensures the task has objective definition before any implementation work begins.

Preventing wrong work involves pausing execution when a request lacks objective definition. You must prompt the requester for key clarifications regarding scope and constraints, seeking explicit user confirmation before proceeding with the implementation.

Pause execution to gather elicitation details whenever a workflow task is underspecified and needs objective definition. This pause ensures essential safety checks, environment requirements, and acceptance criteria are confirmed before moving forward with implementation.

You can proceed with default assumptions if a task scope is underspecified, but execution must pause until the user provides explicit approval. Prompting for must-have questions first ensures the requester confirms or corrects these defaults to prevent wrong work.