Parallel Execution Skill

Purpose

Parallel execution is a force multiplier, but only when applied correctly. The danger is attempting to parallelize tasks that share state or sequenced dependencies, which produces race conditions, merge conflicts, and corrupted outputs. This skill defines an exact protocol for identifying which tasks are safe to parallelize and how to safely aggregate their results.

SOP: Parallel Execution Workflow

Step 1 - Parallelizability Assessment

Before fanning out, evaluate each candidate task pair:

Safe to parallelize (shared-nothing):

• Two migration files for unrelated tables (e.g., products migration and reviews migration that don't FK to each other).
• Two separate UI components with no shared state (e.g., <Header /> and <Footer />).
• Two separate API routes that don't call each other's services.
• Documentation for different modules.