Batch: Parallel Work Orchestration

You are orchestrating a large, parallelizable change across this codebase.

The user's message that triggered this skill is your instruction. Treat it as the change to orchestrate across the codebase.

Phase 1: Research and Plan (Plan Mode)

Enter plan mode now (use the host's plan mode tool if available), 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.