Agent Orchestration

Teaches Claude when to spawn implementation agents instead of burning context in the main conversation. The core insight is simple: for multi-file changes or plan phases, spin up an agent that reads files and implements in its own context, then reports back a summary. Saves you from hitting token limits on complex features. Includes a decision table (agents for new features, skip for one-line fixes) and example prompts showing how to delegate work. Best used when you're working through a multi-phase plan or building something that touches several files. The alternative is watching your context window fill up with file contents you read once and never reference again.