batch-orchestration

by rohitg002.9k

Developer ToolsProductivity

Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

npx skills add rohitg00/pro-workflow --skill batch-orchestration -a cursor -y

Download skill skills/batch-orchestration/SKILL.md on GitHub

Related skills

View all

Questions

How do I install batch-orchestration?: Download skills/batch-orchestration/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does batch-orchestration live?: The publisher keeps it at https://github.com/rohitg00/pro-workflow.
Which agents can use batch-orchestration?: Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.

name: batch-orchestration description: Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern. user-invocable: true

Batch Orchestration

The /batch command pattern for large-scale parallel changes.

How It Works

/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

Use Case	Why Batch Works
API migrations	Same pattern across many endpoints
Dependency upgrades	Find/replace + fix across codebase
Codemod-style refactors	Mechanical transformation, file by file
Adding instrumentation	Same tracing/logging pattern everywhere
Test coverage gaps	Add tests to untested modules independently
Lint rule adoption	Apply new rule fixes across all files

Don't Batch	Why
Interdependent changes	Units can't run in parallel if they depend on each other
Shared state modifications	Multiple agents writing to the same config or state file
Architecture changes	Need holistic reasoning, not file-by-file
Schema migrations	Database changes must be sequential
Changes requiring human judgment per file	Defeats the purpose of automation

Pattern	Scale	Isolation
Direct edit	1-3 files	None needed
Subagent	1 focused task	Forked context
Worktree	1 feature branch	Full repo copy
Agent teams	3-5 parallel tasks	Shared task list
Batch	5-30 identical pattern	Full worktree per unit

batch-orchestration

Install

Related skills

Questions

name: batch-orchestration description: Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern. user-invocable: true

Batch Orchestration

How It Works

Syntax

Phase 1: Research

Phase 2: Decompose

Phase 3: Plan Approval

Phase 4: Execute

Phase 5: Collect

Best For

Anti-Patterns

Relationship to Other Patterns

Guardrails