ask-questions-if-underspecified

To reduce costly assumptions in task execution, you must validate project goals and acceptance criteria with the requestor prior to deployment. Confirming elements like objectives, 'done' criteria, scope, and constraints ensures accurate interpretation and prevents costly rework.

Mitigating risk for underspecified project scope requires a systematic questioning process that expedites accurate interpretation and efficient action planning. By validating project goals and acceptance criteria with the requestor beforehand, you prevent misdirection and ensure accurate, safe task execution.

Preventing rework from misunderstood software development objectives requires identifying underspecified requirements and asking essential clarifying questions beforehand. Validating goals, scope, and acceptance criteria with the requestor ensures work isn't prematurely implemented and saves valuable resources.

Requirement clarification works effectively for technical workflows by ensuring accurate and safe task execution with specific considerations for language version, safety, and reversibility. This process identifies underspecified requirements and asks essential clarifying questions tailored for administrative and technical environments.

You should not proceed with task execution when elements like objectives, 'done' criteria, scope, constraints, and environment are unclear. Halt implementation to ask essential clarifying questions, mitigating the risk of costly rework due to misunderstanding of project objectives.