ask-questions-if-underspecified

To prevent wrong implementation, pause execution and ask targeted clarifying questions. Identifying underspecified objectives, scope, and constraints before taking action ensures the final deliverable matches the actual project requirements.

The best way to clarify ambiguous acceptance criteria is using a gatekeeping mechanism that asks 1 to 5 must-have multiple-choice questions. This provides structured options with default fast-path acceptance to resolve scope ambiguities efficiently.

You enforce a clarification gate by pausing implementation commands and edits until the user provides answers or explicitly approves stated assumptions. This safety-first execution control prevents incorrect planning for engineering tasks with unclear scope.

Yes, you can proceed with development by relying on default assumptions. When environment constraints are missing, the system offers a reply with defaults option, allowing you to fast-path execution by explicitly approving those default assumptions.

You should pause implementation to ask for planning guardrails whenever a request can be interpreted in multiple ways. If safety details, constraints, or acceptance criteria are unclear, pausing prevents wasted effort and wrong outcomes.