orchestrator-mode

You can execute complex plans with parallel subagents by decomposing the work into parallel waves and fanning out subagents. This approach applies gate-based verification between execution waves to ensure work is completed efficiently and safely.

Plan decomposition into parallel waves is an orchestration mechanism that breaks complex workflows into scalable execution batches. It separates the plan from the execution method, allowing subagents to run concurrently while maintaining verification gates between each wave.

To coordinate scalable parallel execution for large workflows, you provide a plan document to an orchestrator. It then decomposes the plan into waves, fans out subagents in parallel, and verifies gates between waves to control execution speed and reliability.

Yes, you need a plan document to use orchestrator-mode because it requires a plan input to function properly. Along with the plan, the workflow requires wave decomposition logic and gate verification rules to decompose and execute the work safely.

You should not use fan-out subagents for workflow orchestration when a complex plan cannot be safely decomposed into parallel waves. Without proper gate verification rules and clear separation between plan and method, controlled parallelism will fail to execute reliably.