Parallel Phase Execution
Execute multiple workflow phases concurrently for faster development cycles
Bootspring supports executing multiple workflow phases in parallel, dramatically reducing overall development time for independent tasks.
Overview#
Traditional workflows execute phases sequentially:
Phase 1 → Phase 2 → Phase 3 → Phase 4
[=====] [=====] [=====] [=====]
Total: 4 units
With parallel execution:
Phase 1 → Phase 2 ──┐
[=====] [=====] │
├── Phase 4
Phase 1 → Phase 3 ──┘ [=====]
[=====] [=====]
Total: 3 units
Parallel-Enabled Workflows#
Full Stack Parallel Development#
Loading code block...
Comprehensive Audit#
Loading code block...
Generate a Parallel Plan (v2.3.4)#
The orchestrator plan action generates structured execution plans via MCP:
Use bootspring_orchestrator action=plan context="Full production audit"
Returns phases marked parallel or sequential with agent assignments and skill references. Claude Code spawns one agent per specialist simultaneously.
Using Parallel Execution#
Starting Parallel Phases#
When you advance into a parallel section, Bootspring automatically detects and starts all parallel phases:
Loading code block...
Completing Individual Phases#
Each parallel phase must be completed individually:
Loading code block...
Checking Parallel Status#
Loading code block...
Best Practices#
Good Candidates for Parallel Execution#
- Frontend and backend development (after API contract)
- Multiple audit types (security, performance, code quality)
- Documentation and testing
- Multi-service deployments
Avoid Parallelizing#
- Phases with data dependencies
- Sequential approval gates
- Database migrations (unless independent)