Batch Modernization Control Plane

This skill owns deterministic batch configuration and state operations. It does not assess source code, generate plans, execute migrations, or invoke MCP tools.

Batch Assessment provides a config-aware multi-repository workflow. modernize is the only public entry. Every new request uses the read-only default-config probe first. When .github/modernize/repos.json exists, the first question always asks Batch or Single, regardless of scope wording; when absent, explicit scope applies and otherwise classic Single remains the default. Configuration discovery never selects Batch or approves execution. Planning, Execution, retry, and takeover scheduling remain disabled. Use only the scripts under scripts/; never edit batch state files manually.

Hard Boundaries

• Deterministic scripts do not invoke agents, MCP tools, Assessment, Planning, or Execution. The internal coordinator owns phase-agent dispatch.
• Do not modify application source or existing Git worktrees.
• Do not stash, switch branches, fetch, rewrite origins, discard changes, push, or create commits.
• Keep credentials out of command-line arguments and persisted files.
• Treat unknown schema versions, malformed inputs, path escapes, wrong owner tokens, and invalid evidence as blocking errors.
• A takeover lease is read-only. It cannot mutate batch state or schedule work until worker fencing exists.
• Batch Assessment starts only attempt 1 for a pending execution unit and permits only one active phase invocation across the batch.

Inputs