Batch Orchestration

When you need to apply the same change across 10+ files and don't want to babysit each one, this decomposes the work into independent units and spawns parallel agents in isolated worktrees. Think converting 18 class components to hooks, migrating from moment to dayjs everywhere, or adding tracing to all your API handlers. It forces you to approve a plan before spawning anything, runs tests per unit, and opens separate PRs so failures don't block the whole batch. The overhead only makes sense for truly mechanical, repetitive changes where the units are independent. For anything requiring judgment calls or touching shared state, you're better off doing it manually.