Orchestration Mastery: Coordinating Five Agents Without Losing the Plot

I can now run five agents in parallel on a single codebase without creating a merge-conflict disaster. Six months ago I could not. The thing that changed was not the agents. It was my coordination discipline.

The Five Failure Modes

1. Two agents editing the same file
2. Two agents installing conflicting dependency versions
3. One agent committing while another is mid-edit
4. The coordinator losing track of what each agent owns
5. The coordinator letting agents negotiate with each other

Every one of these is a coordinator failure, not an agent failure.

The Discipline

Before spawning agents, I draw a dependency graph. Nodes are tasks. Edges are dependencies. Independent nodes can run in parallel. Dependent nodes run in waves. Every parallel agent gets a non-overlapping file scope. The coordinator does not let agents negotiate scope. The coordinator assigns it.

Wave 1 (parallel): agent-A (backend/auth), agent-B (frontend/login-ui)
Wave 2 (parallel): agent-C (backend/tokens), agent-D (frontend/session)
Wave 3 (sequential): agent-E (integration tests, reads all)

The Merge Discipline

Each agent commits to its own branch. The coordinator merges. Agents do not merge their own work. Agents do not review each other. The coordinator is the only entity that reads across branches and decides what ships.

The State Discipline

The coordinator maintains a single state file listing every agent, its task, its scope, its branch, and its status. Agents read the state file on start. Agents update their own row on end. The coordinator reads all rows to decide next waves.

What I Stopped Doing

Letting agents chat with each other. Letting agents propose scope changes. Letting agents write files outside their declared scope. Each of these sounds sophisticated and each of these produces chaos.

The Scaling Ceiling

Five agents is the most I can coordinate with confidence. Above five, the state file becomes a novel and the merge step becomes a bottleneck. Teams that claim to coordinate fifty agents are either lying or have built infrastructure I have not seen. GSD v1.6.4 taught me a lot of this discipline the hard way.

Orchestration is a human skill. The agents are the easy part.