resolve-ambiguity

Core principle: Rather ask than guess. Wrong assumptions waste more time than clarifying questions.

<quick_start> <decision_tree> When you encounter ambiguity, classify it:

1. Technical/Factual - "How does X work?" "What is the correct syntax?" → Likely found in project or online sources → Follow the tiered lookup process

2. Intent/Choice - "Which approach should I use?" "What does the user want?" → Requires user input → Use AskUserQuestion immediately </decision_tree>