parallel-build

To run multiple specs in parallel, you need dependency-aware batching to group independent specs and generate a session plan with terminal commands for concurrent execution. This avoids conflicts and reduces total build time.

Dependency analysis for parallel builds identifies safe parallelization opportunities across multiple specs to prevent conflicts. You need it when executing multiple features concurrently to ensure independent specs are grouped correctly and safely.

Generating a batch execution plan involves analyzing spec dependencies and producing terminal commands for concurrent Claude Code sessions. The plan batches independent work together to enable parallel agents to execute without overlapping.

Yes, parallel-build includes post-build integration verification to ensure all features work together after parallel execution. This step checks the combined output of the batched sessions to catch any integration conflicts.

Parallel-build works across specs specifically stored in the /specs directory. It scans this location to perform dependency analysis, group independent files, and generate the parallel session plan.

When dependency analysis detects conflicts between specs during batching, it prevents those specs from running in the same parallel batch. The tool handles conflicts by grouping only independent specs together to ensure safe concurrent execution.