avoid-acting-on-assumptions

To stop making assumptions with unclear requirements, use a prompt that enforces asking one clarifying question before proceeding with the task. This practice prevents misinterpretation and reduces rework by ensuring you pause to confirm details first.

The best way to clarify ambiguous product specifications is to pause and ask a targeted clarifying question before acting. This approach enforces documenting the agreed clarification path, reducing future misinterpretation and rework.

To prompt for clarifying questions during software development planning, apply a rule that stops action until one question is asked. This mechanism intercepts ambiguous requirements, ensuring details are documented before any development proceeds.

Yes, enforcing a clarifying question works for documentation tasks. When requirements are unclear, pausing to ask one question before drafting prevents acting on assumptions and records the clarification for future reference.

You should ask a clarifying question before acting on vague requests to avoid proceeding with assumptions. This practice reduces rework by documenting the agreed clarification path, ensuring the final output matches actual expectations.