orchestrating-parallel-taskslisted

# SOP: Orchestrating Parallel Tasks ## Purpose Provides a systematic workflow for breaking down "epic-level" requirements into independent sub-tasks. This approach maximizes agent efficiency, enables parallel execution, and minimizes merge conflicts by ensuring clear functional and file-level boundaries. ## Workflow Checklist - [ ] **Step 1: Contextual Analysis** - [ ] Identify high-level architectural layers involved (UI, API, Data, Auth, etc.). - [ ] List existing files likely to be impacted. - [ ] Identify external dependencies (Third-party APIs, DB schemas). - [ ] **Step 2: Boundary Identification & Slicing** - [ ] Apply **Vertical Slicing** to group features by user value. - [ ] Apply **Interface-First** slicing for shared components. - [ ] Identify "Shared Core" vs. "Independent Leaves". - [ ] **Step 3: Mutual Exclusivity Enforcement** - [ ] Verify that no two sub-tasks target the same set of files for modification. - [ ] Decouple shared utilities into their own prerequisite task. - [ ] Define mock interfaces for cross-task dependencies. - [ ] **Step 4: Sub-Task Specification** - [ ] Draft a clear "Acceptance Criteria" for each sub-task. - [ ] Define the "MVP Slice" for each task. - [ ] Map out the dependency graph (which tasks must finish before others start). - [ ] **Step 5: User Validation** - [ ] Present the phased plan and task list to the user for approval. ## Detailed Instructions ### 1. Vertical Slicing vs. Horizontal Slicing Whe