Parallel Execution Optimizer

When you need to move fast without breaking things, this skill teaches Claude to think in dependency graphs and execution lanes. It pushes batched reads, isolated worktrees, and parallel test runs while keeping writes from colliding. The lane matrix is the key idea: before any big push, you map what can run concurrently, what each lane touches, and how you'll verify it worked. This isn't about spawning threads blindly. It's about turning "make it faster" into a plan where independent work happens together and you end with proof, not just a claim that something ran quickly.

skills.sh installs: 5.3K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill parallel-execution-optimizer --agent claude-code

Installs into .claude/skills of the current project.

Files

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. Also use it when homogeneous work repeats unchanged preparation between records, even if the record operations must remain sequential.

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

SKILL.md on GitHub