What problem does it solve?
It turns a planner’s batch of boundary-aware clarifying questions into a validated, routing-to-tools workflow that consistently asks users only the delegated skill can handle, preventing missing fields, bad anchors, and unsupported interaction paths.
Core Features & Use Cases
- Schema-first intake & validation: checks the shared questions payload contract and route-specific payload requirements before dispatching any tool calls.
- Prioritized normalization for better UX: sorts questions by planner-provided
priority_score and translates recommendation rationales into simplified, user-friendly wording.
- Capability-based routing: detects available runtime tooling and routes to either the
specformula-fork flow (when fork is available) or the ask-user-question flow (when ask-question tools are available), failing fast on unsupported tooling.
- Sub-skill delegation: delegates interaction and updates to dedicated sub-skills (
SpecFormula-Fork for fork, AskUserQuestion for interactive rounds with async/sync update modes).
- Failure contract with clear outcomes: returns structured statuses like
incomplete, unsupported_tooling, or route_failed so callers can recover reliably.
Quick Start
Ask the system to run clarify-loop on a planner payload containing questions[] with per-question options, priorities, and (for the chosen route) required fields like location or specformula anchors.
