multi-agent-patterns

1# Multi-Agent Architecture Patterns
2 
3Multi-agent architectures distribute work across multiple language model instances, each with its own context window. When designed well, this distribution enables capabilities beyond single-agent limits. When designed poorly, it introduces coordination overhead that negates benefits. The critical insight is that sub-agents exist primarily to isolate context, not to anthropomorphize role division.
4 
5## When to Activate
6 
7Activate this skill when:
8- Single-agent context limits constrain task complexity
9- Tasks decompose naturally into parallel subtasks
10- Different subtasks require different tool sets or system prompts
11- Building systems that must handle multiple domains simultaneously
12- Scaling agent capabilities beyond single-context limits
13- Designing production agent systems with multiple specialized components
14 
15Do not activate this skill for adjacent work owned by other skills:
16- Deciding task-model fit, pipeline shape, or project-level cost before topology is known: `project-development`.
17- Designing hosted sandboxes, warm pools, remote sessions, or background runtime infrastructure: `hosted-agents`.
18- Sharing orchestrator state through KV-cache compaction in controlled runtimes: `latent-briefing`.
19- Designing the tools each agent exposes: `tool-design`.
20 
21## Core Concepts
22…