orchestrator-mode

Decompose complex plans into parallel waves with gate verification.

Updated Feb 3, 2026

Search Tags:#subagents #orchestrator #parallelism #fan-out #plan-decomposition #wave-decomposition

Ready to run

npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill orchestrator-mode-bedabeda-growth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestrator-mode
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/orchestrator-mode
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill orchestrator-mode-bedabeda-growth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrator-mode solves the problem of executing complex plans by decomposing them into parallel waves and fanning out subagents, ensuring proper gate verification and separation between plan and method.

Core Features & Use Cases

Decompose plans into waves for scalable execution.
Fan-out subagents in parallel with gate verification between waves.
Use Case: Orchestrate large workflows where speed and reliability depend on controlled parallelism.

Quick Start

Provide a plan document to the orchestrator-mode and it will decompose into waves, fan out work, and verify gates.

Frequently Asked Questions about orchestrator-mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I execute complex plans with parallel subagents?▼

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.

What is plan decomposition into parallel waves?▼

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.

How do I coordinate scalable parallel execution for large workflows?▼

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.

Do I need a plan document to use orchestrator-mode?▼

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.

When should I not use fan-out subagents for workflow orchestration?▼

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.