Parallel agent dispatch
Skill jagreehal/jagreehal-claude-skills/skills/parallel-agent-dispatch
Dispatches independent subagents in parallel with clear contracts and merge discipline. Use this skill when multiple independent research or implementation strands can proceed without shared mutable state. Do not use when/for sequential dependent steps, or creating git worktrees themselves (use git-worktrees).From its SKILL.md
npx -y skills add jagreehal/jagreehal-claude-skills --skill parallel-agent-dispatchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, as published. Nobody here has run it
Parallel Agent Dispatch
Critical rules
- Domains must be independent. If failures might share a root cause, use one agent.
- Each agent gets specific scope, clear goal, constraints, and expected output.
- Never ask agents to "make tests pass" without finding the real cause.
- After return: read summaries, check conflicts, run full suite; verify via
verification-before-completion. - Before dispatching, read references/patterns.md.
Workflow
- Confirm independence (no shared state/files; fixing one cannot affect another).
- Group by domain; write one self-contained brief per domain (see patterns).
- Dispatch agents concurrently.
- Review each summary; resolve conflicts.
- Run the full test suite; integrate only after fresh verification.
Decision: multiple failures → independent? no → single agent; yes → can parallelize? no → sequential; yes → parallel dispatch.
Resources
- references/patterns.md — brief template, when to parallelize, mistakes. Read before dispatch.
Validation
Before dispatch:
- Independence confirmed
- Each prompt has scope, goal, constraints, errors, return format
After return:
- Summaries read; conflicts checked
- Full suite passes after integration
Constraints
- Related:
debugging-methodology,verification-before-completion,tdd-workflow,git-worktrees. - Do not parallelize exploratory debugging when you do not yet know what is broken.