resolve-ambiguity

Resolve ambiguity through systematic tiered lookup: start with project context and architecture docs, escalate to MCP references or web sources if needed, and ask users for clarification when authoritative information isn't available. This approach prevents costly guesses in technical or intent-based decisions.

Use tiered lookup for technical or factual ambiguities where existing documentation, references, or sources can provide definitive answers. Reserve user clarification for intent and choice questions where only the user can decide direction, making the process faster and more informed.

Technical ambiguity involves unclear facts or implementation choices resolvable through lookup—architecture docs, APIs, or web research. Intent ambiguity involves user goals or preferences only the user can clarify. Categorizing correctly determines whether to search references or ask the user.

Stop lookup when you find authoritative information that directly answers the ambiguity—a definitive source, specification, or documented pattern. If multiple sources conflict or no source exists, escalate to user clarification rather than continuing to search.

Yes. Apply tiered lookup to architecture decisions by consulting design docs and references, then decide whether the choice is technical (resolvable through lookup) or strategic (requiring user input). This systematic approach reduces decision delays and ensures choices are informed.

Tiered lookup progresses from project context and architecture docs first, then MCP references, then web sources. This sequence prioritizes internal knowledge over external, ensuring locally-relevant decisions and stopping early when authoritative information is found close to the problem.