orchestrate

You manage multiple git worktrees by allocating a dedicated worktree per workstream and tracking each in a distinct manifest. This enables parallel development by isolating concurrent implementers until convergence validation.

Workstream convergence validation is the process of verifying that independently developed worktrees align before merging. It acts as a security review gate and checkpoint to ensure atomic spec discipline across all parallel branches.

Orchestrate subagents by loading the MasterSpec, allocating worktrees for each independent workstream, and dispatching the first implementers into their respective isolated environments. The pipeline tracks progress from atomization to automated merge.

A MasterSpec is required for automated worktree allocation in this context. The orchestration pipeline relies on MasterSpec loading and validation to generate atomic specs and coordinate three or more concurrent workstreams effectively.

The best way to merge parallel git worktrees is through a managed merge queue. After passing convergence validation and security gates, the pipeline drives automated merges with built-in checkpoints and rollback safeguards for post-merge recovery.

You can roll back failed multi-workstream merges using the pipeline's built-in rollback safeguards. The staged workflow includes checkpoints at each phase, from atomization to merge, ensuring controlled recovery if convergence validation fails.