parallel-execution-optimizer
Speed up a task by turning it into a dependency graph of parallel lanes with a lane matrix, batched reads and checks, write surfaces isolated by file, worktree, branch, or service, and a final verification table.
- Kind
- Skill
- Works with
- Claude Code, Codex
- Source
- affaan-m/ECC @ d3b8a3e90890
- Path
- skills/parallel-execution-optimizer/SKILL.md
- License
- MIT
- Jobs
- Git workflow, Automation, Guardrails
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# 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. 1. Define the objective and done signal. 2. Split work into lanes. 3. Mark each lane as parallel, sequential, or gated. 4. Run independent reads/checks together. 5. Keep writes isolated by file, worktree, branch, service, or dataset. 6. Merge only after evidence shows the lanes are compatible. 7. End with a verification table, not a vague speed claim. ## Lane Matrix Before a large push, write a compact matrix: ```text 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 …