avoid-acting-on-assumptions

# Avoid Acting on Assumptions **Mistake pattern:** User says something ambiguous → you assume the most likely interpretation → you deliver something → it's wrong. **Fix:** When requirements are ambiguous, ask ONE clarifying question. The cost of pausing to ask is always lower than the cost of delivering the wrong result. **Especially risky assumptions:** - The target programming language or framework. - Whether a file should be overwritten or appended. - What "clean up" or "improve" means in context. - Whether a test environment or production is the target.