subagent-orchestration
Decompose work across parallel subagents properly — task slicing that avoids collisions, briefs that stand alone, and result integration that catches contradictions. Use when work can genuinely parallelise (research fan-outs, multi-file changes, independent analyses), when deciding whether to delegate or do it yourself, or when past multi-agent runs produced conflicts and duplicated effort. Produces an orchestration plan: the parallel/sequential split, per-agent briefs, and the integration protocol.
npx skills add mohitagw15856/pm-claude-skills --skill subagent-orchestration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Subagent Orchestration Skill Parallel agents multiply speed exactly when the decomposition is right — and multiply mess when it isn't: two agents editing one file, three agents making inconsistent assumptions, results that can't be merged. Orchestration is a design discipline: slice for independence, brief for standalone execution, integrate with suspicion. ## What This Skill Produces - A **decomposition decision**: what runs parallel, what stays sequential, what isn't worth delegating at all - **Per-agent briefs** that survive without shared context - An **integration protocol**: merge order, conflict checks, and the verification of the combined result ## Orchestration Method 1. **Decide IF before HOW.** Delegation costs: brief-writing, context loss, integration, and review of work you didn't watch. Worth it when subtasks are genuinely independent AND individually substantial. A task you could finish in the time it takes to write two good briefs is yours to do. 2. **Slice by ownership boundary, not by topic.** The test per pair of subtasks: do they write to the same artifact, or does one's output change the other's input? Yes → sequential or merged into one task. The safe cuts:
- What This Skill Produces
- Orchestration Method
- Output Format
- Orchestration plan: [task]
- Quality Checks
- Anti-Patterns
What does the subagent-orchestration skill do?
Decompose work across parallel subagents properly — task slicing that avoids collisions, briefs that stand alone, and result integration that catches contradictions. Use when work can genuinely parallelise (research fan-outs, multi-file changes, independent analyses), when deciding whether to delegate or do it yourself, or when past multi-agent runs produced conflicts and duplicated effort. Produces an orchestration plan: the parallel/sequential split, per-agent briefs, and the integration protocol.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill subagent-orchestration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.