multi-agent-patternslisted

# Multi-Agent Architecture Patterns Multi-agent architectures distribute work across multiple language model instances, each with its own context window. The critical insight is that sub-agents exist primarily to isolate context, not to anthropomorphize role division. ## When to Activate - Single-agent context limits constrain task complexity - Tasks decompose naturally into parallel subtasks - Different subtasks require different tool sets or system prompts - Building systems that must handle multiple domains simultaneously - Scaling agent capabilities beyond single-context limits - Designing production agent systems with multiple specialized components Do not activate this skill for adjacent work owned by other skills: - Designing the tools each agent exposes: `tool-design`. ## Core Concepts Use multi-agent patterns when a single agent's context window cannot hold all task-relevant information. Context isolation is the primary benefit — each agent operates in a clean context without accumulated noise from other subtasks, preventing the telephone game problem where information degrades through repeated summarization. Choose among three dominant patterns based on coordination needs, not organizational metaphor: - **Supervisor/orchestrator** — Use for centralized control when tasks have clear decomposition and human oversight matters. A single coordinator delegates to specialists and synthesizes results. - **Peer-to-peer/swarm** — Use for flexible exploration when rig