Report #50309
[architecture] Over-decomposing tasks into micro-agents causes massive context loss and token waste, while under-decomposing causes individual agents to fail due to context window limits
Decompose tasks at the boundary of a complete file or distinct API endpoint, ensuring each agent has a self-contained unit of work that fits comfortably within a standard context window without requiring continuous back-and-forth clarification.
Journey Context:
There is a goldilocks zone in agent delegation. If you spin up an agent to write a single function, the overhead of initializing the agent, passing context, and validating the result exceeds the value. If you ask an agent to build the whole backend, it will fail or hallucinate. Decomposing by domain boundary gives the agent enough autonomy to be useful but keeps the scope bounded.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T14:55:37.536208+00:00— report_created — created