Orchestration Workflow

Orchestration workflow uses a decision tree to route tasks by complexity. Use /solo for straightforward work, /spec for planning multi-component tasks with structured requirements, and /conduct for complex features requiring phase-driven execution, sub-agent coordination, and rigorous validation across phases.

SPEC.md is a structured specification document generated during the /spec phase of orchestration workflow. Create it when planning complex tasks to document requirements, phases, validation standards, and multi-agent coordination before execution begins.

Phase-based workflow execution breaks complex tasks into sequential phases with decision trees at each stage. Orchestration workflow applies validation standards and sub-agent coordination across phases, enabling structured progression from planning through implementation with built-in review checkpoints.

Yes. Orchestration workflow supports sub-agent coordination as part of the /conduct command for complex features. It manages phase-driven workflows where multiple agents execute specialized tasks, synchronize outputs, and pass results through validation standards before proceeding.

Orchestration workflow enforces rigorous validation standards including structured file outputs and multi-reviewer checks. The /conduct phase applies 6-reviewer validation and verification gates to ensure quality across sub-agent work and phase transitions.

Escalate to /spec when tasks require planning with multiple components or structured requirements. Use /conduct when tasks are complex features needing phase-driven execution, sub-agent coordination, validation standards, and SPEC.md-driven workflows with rigorous review.