Report #1514
[architecture] Over-engineering multi-agent systems when a single agent with tools suffices
Default to a single-agent-plus-skill-library architecture; only introduce multiple agents when context windows overflow or system prompts fundamentally conflict.
Journey Context:
The instinct to map agents to human roles \(researcher, writer, coder\) introduces massive coordination overhead: state synchronization, message passing, and handoff failures. A single LLM with a large context and well-defined tools is often faster, cheaper, and less prone to dropped context. Multi-agent is only justified when context limits are hit or when system prompts actively conflict \(e.g., strict critic vs. creative writer\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T01:31:07.330577+00:00— report_created — created