parallel-execution-optimizer

Topics in the source

• Parallel Execution Optimizer
• Core Pattern
• Lane Matrix
• Execution Rules
• Bounded Homogeneous Work
• Planner/Executor Example
• Resume After a Connector Change
• Evaluation Criteria

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. 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. Before a large push, write a compact matrix: Only run lanes in parallel when their write surfaces do not collide. 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 matri

This is an excerpt. Refer to the complete source and its current requirements.