parallel-execution-optimizer
/parallel-execution-optimizer
Use when the user wants a task done much faster through parallel work, concurrent agents, batched tool calls, isolated worktrees, or many independent verification lanes without losing correctness.
- Author
- ysyecust ↗
- Repository
- everything-claude-code ↗
- Licence
- MIT
- Last repository change
- 06.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when the user wants a task done much faster through parallel work, concurrent agents, batched tool calls, isolated worktrees, or many independent verification lanes without losing correctness.
Original author description
Use when the user wants a task done much faster through parallel work, concurrent agents, batched tool calls, isolated worktrees, or many independent verification lanes without losing correctness.
How it works
- Core Pattern
- Lane Matrix
- Execution Rules
- Output Shape
- Failure Modes
SKILL.md preview
--- name: parallel-execution-optimizer description: Use when the user wants a task done much faster through parallel work, concurrent agents, batched tool calls, isolated worktrees, or many independent verification lanes without losing correctness. metadata: origin: ECC tools: Read, Write, Edit, Bash, Grep, Glob --- # 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 - Batch file reads, searches, status checks, and metadata queries. - Use isolated worktrees for large unrelated implementation lanes. - Start long-running tests, builds, backfills, and deploys in separate sessions, then poll them deliberately. - If a lane discovers a blocker that changes the plan, pause dependent lanes and update the matrix. - Never let a background process outlive the turn unless the user explicitly asked for a continuing service. - Do not parallelize destructive commands, migrations, writes to the same table, or live customer-impacting deploys without an explicit gate. ## Output Shape Use this when reporting: ```text Parallel execution result: - Lanes run: 5 - Lanes completed: 4 - Blocked lane: deploy readback, waiting on DNS propagation - Fast path found: batched repo scan + focused tests - Verification: lint pass, unit pass, live smoke pass ``` ## Failure Modes - More concurrency that creates conflicting edits. - Benchmarking the tool instead of the task. - Treating "fast" as done before correctness is proven. - Forgetting to poll running sessions. - Hiding skipped checks behind a success summary.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ysyecust/everything-claude-code | 100 | MIT |
| kannnnna9/ultracode | 100 | MIT |
| affaan-m/ECC | 96 | MIT |
| marcusgoll/Spec-Flow | 87 | MIT |
| marcusgoll/Spec-Flow | 87 | MIT |
Database snapshot: 13.11.2026 · package version 4af461ce4d63 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100parallel-lanes
Split browser work across parallel lanes. Use when a task touches several independent sites or several independent records, when the user asks to run things in parallel, or when a sequential browser plan would take more than a few minutes. - 92task-partitioner
This skill should be used when the user asks to "partition tasks for parallel agents", "plan multi-agent execution", "create dependency graph", or before spawning any parallel agents. Produces a dependency graph, disjoint file ownership map, and batched execution groups to… - 100agent-spawn
Use when launching parallel tmux agents with optional isolated Git worktrees under Oh My Harness. - 100lanes
Set, increase, or decrease the parallel lanes of a meta-orchestrator run by grouping queued issues into file-disjoint streams, with a cost line and a confirm step. Use for "/lanes 3", "more lanes" / "go faster in parallel", "fewer lanes", or when meta-orchestrator setup reaches `parallel:`. - 100parallel-execution-engine
Use when latency matters and several independent tasks can run at once -- a bounded implementation or investigation that needs waves of concurrent workers, not a persistent completion loop or stage-based orchestration. - 100parallel-task
Coordinate plan files by launching multiple parallel subagents for unblocked tasks. Triggers on explicit "/parallel-task" commands.