Parallel Execution Optimizer
Use this skill when speed comes from doing independent work at the same time: repo inspection, file reads, API checks, browser checks, build/test lanes, deploy readbacks, or multi-worktree implementation passes.
Core Pattern
Turn urgency into a dependency graph before acting.
- Define the objective and done signal.
- Split work into lanes.
- Mark each lane as parallel, sequential, or gated.
- Run independent reads/checks together.
- Keep writes isolated by file, worktree, branch, service, or dataset.
- Merge only after evidence shows the lanes are compatible.
- End with a verification table, not a vague speed claim.
Lane Matrix
Before a large push, write a compact matrix:
Lane | Can run in parallel? | Write surface | Risk | Verification
Repo scan | yes | none | low | rg/git status outputs
Backend patch | maybe | src/api | medium | unit tests
Frontend patch | maybe | app/components | medium | browser screenshot
Deploy readback | after build | remote service | high | live URL + logs
Only run lanes in parallel when their write surfaces do not collide.
Execution Rules
- Batch file reads, searches, status checks, and m…
