Parallel Task Execution: $ARGUMENTS

Pre-Flight Check

1. Identify all distinct tasks from: "$ARGUMENTS"
2. Verify tasks don't have dependencies on each other
3. Ensure tasks operate on DIFFERENT files (no conflicts)

Parallel Execution Strategy

For each independent task, spawn a @task-worker agent:

Task Distribution:
- Worker 1: [task] -> [files]
- Worker 2: [task] -> [files]
- Worker 3: [task] -> [files]

Orchestration Rules

• Independent files: Each worker handles separate files
• No overlapping edits: Assign non-conflicting regions
• Clear boundaries: Define exactly what each worker does

Conflict Prevention

• Workers edit different files
• If same file needed, sequence instead of parallel
• Orchestrator handles coordination

Execution Flow

     Orchestrator (You)
     Plans & Coordinates
            |
    +-------+-------+
    |       |       |
   W1      W2      W3   (Haiku @task-workers)
  FileA   FileB   FileC

Completion Checklist

1. Wait for all workers to complete
2. Verify no conflicts in changes
3. Run quality checks: typecheck, lint
4. Report aggregate results

Output Format

## Parallel Execution Report

Tasks Executed: [N]
Workers Used: [N]

### Results
- Worker 1: [status] [task] - [files]
- Worker 2: [status] [task] - [files]

### Quality Check
- Typecheck: [PASSED/FAILED]
- Lint: [PASSED/FAILED]

### Summary
[Overall outcome]