parallel-work

name	parallel-work
description	Fan-out/fan-in patterns for parallel agent work. Writer/reviewer pattern, conflict resolution, quality verification across parallel sessions. Use when working on multi-file changes or large migrations. Triggers: "parallel", "fan-out", "migration", "batch", "multi-file".
category	agent-patterns

Skill: parallel-work

What This Covers

Patterns for distributing work across multiple parallel agent sessions. Useful for large migrations, multi-file changes, and codebase-wide refactoring.

Fan-Out Pattern

For large migrations or multi-file changes:

1. Generate Task List

# List all files needing changes
find src/ -name "*.js" > files.txt
wc -l files.txt

2. Loop Through Tasks

for file in $(cat files.txt); do
  bun run agent:check "$file"
done

3. Test on a Few First

# Test on 2-3 files first
head -3 files.txt | while read file; do
  echo "Processing: $file"
  # ... process file ...
done

4. Run at Scale

# Run on full list
cat files.txt | while read file; do
  echo "Processing: $file"
  # ... process file ...
done

Writer/Reviewer Pattern

Session A (Writer)	Session B (Reviewer)
Implement feature	Review diff for edge cases
Address feedback	Re-review after fixes
Commit when green	Verify quality gates

Writer Session

# Implement changes
# ... code ...

# Run tests
bun vitest run

# Run quality gate
bash scripts/quality-gate.sh

Reviewer Session

# Review the diff
git diff

# Check for edge cases
# ... review ...

# Run adversarial review
# Review the diff for edge cases, security issues, and convention violations.
# Report gaps that affect correctness, not style preferences.

Conflict Resolution

When parallel sessions modify the same files:

1. Detect: git status shows conflicts
2. Analyze: Read both versions
3. Merge: Combine logically (not just concatenation)
4. Test: Run bun vitest run
5. Verify: Run bash scripts/quality-gate.sh

Quality Verification Across Parallel Work

# After parallel work completes
bash scripts/quality-gate.sh
bash scripts/roast-scorer.sh
bash scripts/doctor.sh

When to Use Parallel Work

Scenario	Pattern
Large migration (100+ files)	Fan-out
Code review	Writer/Reviewer
Multi-feature development	Fan-out with coordination
Refactoring	Fan-out with verification

Rules

• Test on a few files first, then run at scale
• Always run quality gates after parallel work
• Use --allowedTools to scope permissions for batch operations
• Detect and resolve conflicts before committing