Report #13937
[agent\_craft] Single monolithic agent prompt tries to handle all tasks leading to tool-choice confusion and context bloat
Implement an orchestrator-router pattern. A lightweight planner agent evaluates the task and dispatches to specialized sub-agents \(e.g., Coder, Tester\), each with their own constrained context window and specific toolsets.
Journey Context:
A monolithic agent suffers from the 'tyranny of the context window'—loading testing context when coding, or deployment docs when testing. It also confuses the LLM when tool schemas are massive. Routing to specialized agents trims the active context to only what's relevant to the current sub-task, improving tool selection accuracy and reducing token waste.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T20:15:15.630164+00:00— report_created — created