parallel-agent-dispatch
/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).
- Author
- jagreehal ↗
- Repository
- jagreehal-claude-skills ↗
- Licence
- MIT
- Last repository change
- 30.07.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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).
Original author description
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).
How it works
- Critical rules
- Workflow
- Resources
- Validation
- Constraints
SKILL.md preview
--- name: parallel-agent-dispatch description: >- 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). version: 1.2.0 --- # 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](references/patterns.md). ## Workflow 1. Confirm independence (no shared state/files; fixing one cannot affect another). 2. Group by domain; write one self-contained brief per domain (see patterns). 3. Dispatch agents concurrently. 4. Review each summary; resolve conflicts. 5. 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](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.
Files in this package (2)
- SKILL.md 2 KB
- references/patterns.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jagreehal/jagreehal-claude-skills | 90 | MIT |
| laurigates/claude-plugins | 100 | MIT |
Database snapshot: 13.11.2026 · package version 1674a0f4d741 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100swarm
Use to dispatch multiple parallel subagents on independent tasks. Discipline around isolation, conflict resolution, merge strategy. Wraps native parallel Task dispatch with structured gates. - 100loom-dispatching-parallel-agents
Dispatch multiple independent tasks to parallel subagents when no shared file conflicts exist. Use when: a confirmed plan has independent tasks that can run concurrently without touching shared files. - 90trove-dispatch
Parallel-agent dispatch workflow. Use when a request contains multiple independent tasks that can be safely delegated. - 100agent-native
Dispatch independent tasks to parallel workers or subagents without write collisions. Use when: running or planning agents in parallel, even two; check scopes before any launch. - 100dispatch-multiple-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies. Dispatch subagents to work concurrently. - 100dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies