Parallel Execution

Minimize wall-clock time without weakening the caller's authority, validation, or reproducibility gates. The caller owns synthesis, every mutation, and the final report.

Workflow

1. Qualify the fan-out

Require a fixed brief and at least two read-only units with explicit scope, output, dependencies, and stop conditions. Otherwise return them for serial execution.

Use subagents for judgement or separate context. Run deterministic lint, typecheck, test, and build commands concurrently only when they cannot mutate shared caches, outputs, ports, databases, simulators, or repository state; otherwise serialize them.

Never delegate from a worker. Without parallel subagents, return control; the caller continues serially.

2. Build the schedule

Map dependencies and the ready frontier. Treat planning evidence as provisional until revalidated against live state.

Reserve the manager's capacity. Use one shared budget for the complete top-level run; nested caller skills consume its remaining slots rather than opening another pool. Run at most four workers concurrently, or fewer when the harness exposes fewer free slots. Queue the remainder.