batch-orchestration
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
With your agent
Install OMGSkills skill "rohitg00/pro-workflow:skills/batch-orchestration" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/rohitg00/pro-workflow /tmp/pro-workflow && ln -s /tmp/pro-workflow/skills/batch-orchestration ~/.claude/skills/batch-orchestrationFrom README
Batch Orchestration The /batch command pattern for large-scale parallel changes. How It Works Syntax The instruction should describe the change pattern, not individual files. The batch system finds the files. Phase 1: Research The orchestrator scans the repo to find every instance that matches the instruction: It builds a complete list of targets and groups them by independence. Phase 2: Decompose Each unit must be: Independent — no shared state with other units Self-contained — can be implemented and tested alone Verifiable — has a clear pass/fail criteria Good units: Bad units: Target 5-30 units. Fewer than 5 doesn't justify the overhead. More than 30 and coordination costs grow. Phase 3: Plan Approval The orchestrator presents: Wait for approval. Never spawn agents without explicit confirmation.
More from this repo
context-engineering
Master the four operations of context engineering — Write, Select, Compress, Isolate.
auto-setup
Auto-configure quality gates, hooks, and settings for a new project.
bug-capture
Capture a user-reported defect as a durable GitHub issue written in the project's own domain language.