parallel-build

Compare multiple implementation approaches by setting up isolated per-approach folders and running them in parallel via agents. This side-by-side testing evaluates speed, complexity, and tradeoffs to select the optimal solution.

Use parallel experimentation when task requirements are ambiguous and a heuristic single-path approach would be risky. It is applicable when there is no obvious best path and multiple viable approaches should be evaluated.

Set up parallel testing by creating isolated per-approach folders for three or more implementation strategies. Coordinate parallel execution via agents to explore the approaches simultaneously and determine the optimal solution.

The best way to evaluate ambiguous requirements is parallel exploration of multiple approaches. This builds confidence by comparing results, including speed, complexity, and tradeoffs, before executing a final winner merge workflow.

Yes, parallel testing requires isolated per-approach folders to ensure clean execution. This isolation allows agents to run multiple implementations simultaneously without interference before the final winner merge workflow.

A single-path heuristic is risky when requirements are ambiguous because it commits to one viable approach without comparison. Parallel evaluation avoids this limitation by side-by-side comparing speed, complexity, and tradeoffs to find the optimal solution.