orchestrating-parallel-agentslisted

# Orchestrating Parallel Agents Spawn multiple Claude agents to work on related issues concurrently using git worktrees. ## Philosophy - **Issues ARE the prompts** - Write issues with enough context for autonomous work - **Maximize parallelism** - Group independent work into waves - **Fail fast** - Complete git/PR manually if agents can't - **Trust but verify** - Review diffs, resolve conflicts manually ## Workflow Checklist Copy and track progress: ``` Parallel Agent Orchestration: - [ ] 1. Break feature into issues (1-3 files each) - [ ] 2. Organize into waves (independent → dependent) - [ ] 3. Pre-approve git permissions in settings.local.json - [ ] 4. Spawn wave with --print flag - [ ] 5. Monitor progress - [ ] 6. Complete stragglers manually - [ ] 7. Merge PRs (rebase between same-file conflicts) - [ ] 8. Cleanup worktrees ``` ## Issue Template Each issue should be completable in isolation: ```markdown ## Problem What's broken or missing. ## Solution High-level approach. ## Files to Modify - `path/to/file` - what changes ## Implementation Code snippets or pseudocode. ## Acceptance Criteria - [ ] Testable outcomes ``` **Key:** Include file paths and code examples. Agents work best with concrete starting points. ## Wave Organization ``` Wave 1: Independent changes (no shared files) Wave 2: Changes that may touch same files (expect conflicts) Wave 3: Integration/testing (depends on all above) ``` **Rule:** Same-file issues go in different waves OR same agen