batchlisted

# Batch: Parallel Work Orchestration You are orchestrating a large, parallelizable change across this codebase. ## User Instruction $ARGUMENTS ## Phase 1: Research and Plan (Plan Mode) Call the `EnterPlanMode` tool now to enter plan mode, then: 1. **Understand the scope.** Launch one or more subagents (in the foreground — you need their results) to deeply research what this instruction touches. Find all the files, patterns, and call sites that need to change. Understand the existing conventions so the migration is consistent. 2. **Decompose into independent units.** Break the work into 5–30 self-contained units. Each unit must: - Be independently implementable in an isolated git worktree (no shared state with sibling units) - Be mergeable on its own without depending on another unit's PR landing first - Be roughly uniform in size (split large units, merge trivial ones) Scale the count to the actual work: few files → closer to 5; hundreds of files → closer to 30. Prefer per-directory or per-module slicing over arbitrary file lists. 3. **Determine the e2e test recipe.** Figure out how a worker can verify its change actually works end-to-end — not just that unit tests pass. Look for: - A `claude-in-chrome` skill or browser-automation tool (for UI changes: click through the affected flow, screenshot the result) - A `tmux` or CLI-verifier skill (for CLI changes: launch the app interactively, exercise the changed behavior) - A dev-server + curl pattern