ambiguity-gate

You can detect ambiguity by scoring request clarity across factors like scope, technical specificity, acceptance criteria, constraints, and context on a 0.0–1.0 scale. This analysis outputs a gate decision and targeted clarifying questions.

A routing gate is a conversational pre-check that evaluates request ambiguity before task delegation. It scores clarity from 0.0 to 1.0 across scope, constraints, and context, deciding whether to proceed or prompt for clarifications.

Generate targeted, open-ended clarifications by analyzing request gaps across technical specificity and acceptance criteria. The system produces up to three clarifying questions to resolve ambiguity for downstream agents.

Yes, ambiguity scoring supports task delegation across multiple domains by evaluating scope clarity and constraints. It computes a 0.0–1.0 score to gate routing pipelines, ensuring requests meet specificity thresholds before implementation.

Ambiguity scores are determined by five factors: scope clarity, technical specificity, acceptance criteria, constraints, and context. These factors combine into a 0.0–1.0 score to guide downstream routing decisions.

Use an ambiguity pre-routing analyzer when delegating requests to downstream agents across multiple domains. It prevents misinterpretation by scoring clarity and surfacing up to three clarifying questions before implementation.