workflow-orchestration

Workflow orchestration coordinates structured thinking and multi-agent parallel execution by distributing independent tasks across waves, applying objective quality gates at each stage, and consolidating results. Use the /workflow command to define task dependencies, enable parallelism where safe, and manage gating between stages.

Orchestration applies a six-step model—Gating, Context Discovery, Analysis & Planning, Parallel Execution, Validation, and Reporting—to break down multi-step projects and multi-file refactors into structured phases with built-in checkpoints. This ensures coordinated planning and execution across distributed work.

Yes. The orchestration model includes explicit Validation and Gating stages that enforce objective quality checks between workflow steps. Use the --validate flag to run validation gates and ensure outputs meet requirements before proceeding to the next phase.

Workflow orchestration front-loads Context Discovery and Analysis & Planning phases before execution begins. Commands like /think and /ultrathink with the --deep and --research flags support structured exploration and reasoning, producing a validated plan before parallel execution starts.

Use orchestration when tasks are multi-step, involve multiple agents or independent work streams, require coordinated planning, or need intermediate validation gates. It's most valuable for architectural decisions, large refactors, and projects where parallel execution and structured checkpoints reduce risk and improve outcomes.