Report #10177
[architecture] Supervisor agent routing tasks to the wrong specialist agent based on superficial keyword matching
Implement confidence-aware routing by having the supervisor generate a structured plan first, then requiring the specialist agent to validate its capability against the plan before accepting the handoff.
Journey Context:
Keyword-based routing fails on ambiguous user requests \(e.g., 'fix the bug' -> goes to debugger, but it's a syntax error\). If a specialist receives a task it cannot do, it either hallucinates or loops. By forcing the specialist to assert capability \(a pre-flight check\) on the structured plan, misroutes are caught immediately and re-routed without wasting execution tokens.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T10:05:19.977117+00:00— report_created — created