Ask when requirements are ambiguous

Updated 2026-02-14

When the request is vague or has multiple interpretations, ask for clarification before implementing. Use in any AI-assisted editor.

Use in Cursor, Windsurf, Codeium, or any AI-assisted editor.

Rule

# Ask when requirements are ambiguous

When the user's request is vague or could be interpreted in multiple ways, ask for clarification before implementing.

- **Examples:** "Add validation" (what rules? which fields?), "Improve performance" (which path? what metric?), "Fix the bug" (which behavior is wrong? what is the expected result?).
- **Do:** Ask one or two short questions to narrow scope, or suggest a minimal interpretation and offer to expand if needed.
- **Do not:** Pick an arbitrary interpretation and build something the user did not want.