batch-orchestrationlisted

# Batch Orchestration The `/batch` command pattern for large-scale parallel changes. ## How It Works ```text /batch <instruction> │ ├── 1. Research: scan repo, understand scope ├── 2. Decompose: split into 5-30 independent units ├── 3. Present plan: show units, ask for approval ├── 4. Execute: one background agent per unit in isolated worktree └── 5. Collect: each agent runs tests and opens a PR ``` ## Syntax ```bash /batch Convert all React class components to function components /batch Add error boundaries to every page component /batch Migrate from moment.js to dayjs across the codebase /batch Add OpenTelemetry tracing to all API handlers ``` The instruction should describe the change pattern, not individual files. The batch system finds the files. ## Phase 1: Research The orchestrator scans the repo to find every instance that matches the instruction: ```bash grep -r "class.*extends.*Component" --include="*.tsx" -l ``` It builds a complete list of targets and groups them by independence. ## Phase 2: Decompose Each unit must be: - **Independent** — no shared state with other units - **Self-contained** — can be implemented and tested alone - **Verifiable** — has a clear pass/fail criteria **Good units:** ```text Unit 1: Convert src/components/Header.tsx (class → function) Unit 2: Convert src/components/Footer.tsx (class → function) Unit 3: Convert src/components/Sidebar.tsx (class → function) ``` **Bad units:** ```text Unit 1: Convert all componen