resolve-ambiguity

To resolve technical ambiguities, systematically gather information through tiered lookups across project files, upstream specifications, and external documentation, prioritizing information retrieval over assumption to ensure accurate decision-making.

The best way to clarify unclear implementation choices is to perform tiered information gathering across documentation and external sources, then intelligently ask users for direct input when information is unavailable or requires a subjective decision.

You need to ask users for clarification during information gathering when answers cannot be found in project documentation, upstream specifications, or external sources, or when resolving uncertain implementation choices requires a subjective decision.

Tiered lookup works by systematically searching project files first, then upstream specifications, and finally external documentation to find unknown context, ensuring accurate decision-making before proceeding with implementation.

Yes, you can use this approach to find exact API endpoints by systematically checking project config files, then architecture docs, and if still not found, asking the user for the correct endpoint to resolve the ambiguity.

Automated clarification cannot resolve subjective decisions or ambiguities where information is entirely absent from project files, upstream specifications, and external documentation without relying on direct user input to proceed accurately.