Coordinate parallel subagents for complex multi-lane tasks

Orchestrate coordinates substantial work by decomposing tasks into distinct, bounded assignments for focused subagents, then integrates their outputs into a single verified result. The coordinator remains available to the user throughout and retains responsibility for the final deliverable, including conflict resolution and verification.

Use Orchestrate when a task has multiple independent research, review, or implementation lanes that can run in parallel to materially reduce elapsed time or improve coverage. Use it when a coordinator must synthesize several bounded outputs into one verified result.

Do NOT use Orchestrate for trivial tasks; keep those with the coordinator. Avoid parallel agents when the task is not substantial enough to justify the added cost and coordination overhead.

The user provides a substantial task that can be decomposed into distinct lanes. The coordinator decomposes it into bounded assignments with explicit outputs, each with all scoped context and evidence required.

The user receives an integrated, verified result after the coordinator resolves conflicts among subagent outputs and completes final verification. Approvals and externally consequential decisions remain with the user.

The coordinator follows a six-step workflow:

1. Decompose the task into distinct, bounded assignments with explicit outputs
2. Run narrow, read-only scouts in parallel with low reasoning effort and no inherited conversation when the runtime supports those controls, giving each scout all scoped context and evidence
3. Use medium reasoning effort for routine implementation and high reasoning effort for difficult work
4. Give each subagent distinct ownership, prevent overlapping assignments, and instruct leaf workers not to delegate
5. Integrate the outputs, resolve conflicts, and verify the combined result
6. Keep approvals and externally consequential decisions with the user

For a repository-wide feature, assign non-overlapping agents to architecture inspection, implementation, and test review, then integrate their findings and run final verification from the coordinator. For a research brief, assign independent sources or questions to read-only scouts, reconcile disagreements, and keep final judgment with the coordinator.

Orchestrate requires a runtime that exposes subagent or delegation tools; otherwise keep the work with the coordinator. Delegation does not authorize file mutations, public actions, purchases, or other consequential operations beyond the user's original scope. Parallel agents add cost and coordination overhead, so use them only when the task is substantial enough to benefit. The coordinator remains responsible for checking claims, changes, tests, and the final answer.