ambiguity-gate

Ambiguity scoring analyzes user requests by evaluating scope, technical specificity, and acceptance criteria on a 0.0 to 1.0 scale. This pre-routing validation ensures agent tasks are well-defined before execution to minimize project rework.

The best way to prevent scope creep from vague requests is applying proactive constraint validation and Socratic questioning to quantify request clarity. This identifies missing constraints and prompts users for necessary details before implementation begins.

You generate targeted questions to resolve request ambiguity automatically by using Socratic clarification mechanisms within an ambiguity analysis workflow. This automatically produces high-impact questions addressing missing technical or acceptance criteria.

You need to apply constraint validation in a pre-routing workflow when user requests lack specific constraints or acceptance criteria, such as broad prompts like making a dashboard better. This ensures proactive validation before agent execution.

Yes, ambiguity analysis works without external dependencies or components, as it operates as a standalone skill. It directly analyzes the text of user requests to score clarity and generate clarification questions independently.