fleet

Parallel ship tasks for decomposed PRDs are coordinated by analyzing cross-feature file conflicts and batching non-conflicting work into isolated worktrees. The system builds a conflict graph, assigns batches via greedy coloring, and merges results back into main.

Conflict-aware batching is a technique that analyzes file overlaps between decomposed PRD features, groups non-conflicting work into parallel execution batches, and uses isolated worktrees to prevent cross-feature interference during automated merging.

Multi-feature PRD ships are orchestrated by reading a decomposition manifest, building a conflict graph, assigning execution batches via greedy coloring, and coordinating per-feature agents in isolated worktrees with automated merging and status updates.

Yes, parallel worktrees can be limited using the --max-parallel option. You can also use --dry-run for planning and conflict analysis without execution, or --batch-only to stop after batch assignment.

Automated merging back into main includes conflict detection with graceful fallback. If conflicts are detected during the merge process, the system falls back safely rather than forcing a problematic merge.

Batch-only mode should be used when you want to review the batch assignment and conflict graph before execution. It stops the fleet workflow after assigning batches via greedy coloring, prior to launching per-feature agents in worktrees.