implementation-orchestration

Automate implementation lifecycle management by orchestrating sub-agents to handle coding, validation, and decomposition. This process manages worktrees, branch creation, and phase dependencies, ensuring the orchestrator supervises the workflow without writing code directly.

Yes, you can use Git worktrees to isolate parallel implementation phases. The orchestration workflow creates and cleans up dedicated Git worktrees and branches for each phase, safely handling both sequential and parallel execution while managing blocked dependencies.

Orchestrate sub-agents for coding and validation by intelligently spawning 'implement' and 'validator' agents. The orchestrator remains in a supervisory role, triggering decomposition for complex phases and using validation gates to ensure code quality at each step before integration.

Yes, workflow orchestration requires Git and a task execution environment capable of spawning sub-agents. These prerequisites allow the system to handle branch management, trigger decomposition workflows, and track progress by updating plan documents with phase completion status.

Phase dependency handling works by managing the sequential and parallel execution of implementation phases. The orchestration protocol analyzes dependencies, addresses blocked tasks, and triggers decomposition workflows when specific phases become too complex to execute directly.

The orchestrator avoids writing code to maintain a strict supervisory role during the implementation lifecycle. It delegates all coding and testing to spawned 'implement' sub-agents, relying on validation gates and progress tracking to ensure quality and correct integration.