parallel

Concurrent development tasks can run without state collisions by fanning out independent, file-disjoint work into isolated git worktrees. This prevents branch state collisions and enables safe parallel execution within a track-based workflow.

The best way to parallelize independent bugfixes in a feature track is to dispatch them concurrently into isolated worktrees. This allows simultaneous execution rather than waiting for each task to complete sequentially.

Automated integration merges concurrent worktree results back into the main track branch atomically. It includes cross-member seam review and seam-checking to ensure consistency across parallelized task execution and branch merging.

Yes, orchestrating worktree-isolated subagents requires a state-machine-driven environment to ensure consistency across parallelized task execution and branch merging. This manages the lifecycle of wave dispatch and atomic integration.

Worktree wave parallelism should not be used when development tasks are not independent or file-disjoint. It is designed specifically for safe, concurrent execution of independent tasks to prevent state collisions within a track-based workflow.

Yes, you can orchestrate worktree-isolated subagents for file-disjoint chores by invoking the conductor parallel command followed by the track name. It manages wave dispatch and automated integration for simultaneous execution.