imabusyman/dispatching-parallel-agents
prompts/squad/skills/dispatching-parallel-agents/SKILL.md
Automatically dispatch multiple agent subtasks in parallel based on file-lock disjointness. Compute task dependencies, validate no file conflicts, emit parallel delegation handoffs. Use this when the Conductor or Orchestrator has multiple independent Coder/Tester tasks to farm out simultaneously.
development
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add imabusyman/CodebrewRouter dispatching-parallel-agentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 7:19 PM121.9s1 file scanned
SKILL.md
- name:
- dispatching-parallel-agents
- description:
- Automatically dispatch multiple agent subtasks in parallel based on file-lock disjointness. Compute task dependencies, validate no file conflicts, emit parallel delegation handoffs. Use this when the Conductor or Orchestrator has multiple independent Coder/Tester tasks to farm out simultaneously.
Dispatching Parallel Agents — automate task assignment
Manages the mechanics of launching multiple agents in parallel without manual file-conflict checking.
When to use
- The plan lists multiple implementation steps with non-overlapping file sets.
- The Conductor or Orchestrator wants to parallelize those steps.
- You need to validate that parallel execution won't cause merge conflicts.
Workflow
Input
A plan with steps like:
## Step 1: Add GeminiProvider class
Files: Blaze.LlmGateway.Infrastructure/Providers/GeminiProvider.cs (create)
## Step 2: Add GeminiProvider tests
Files: Blaze.LlmGateway.Tests/Providers/GeminiProviderTests.cs (create)
## Step 3: Wire GeminiProvider in AppHost
Files: Blaze.LlmGateway.AppHost/Program.cs (edit)
Analysis
- Extract file sets from each step.
- Check for conflicts: Do any two steps touch the same file? If yes, they must be sequential.
- Topologically sort: Group non-conflicting steps into "phases."
- Assign to agents: Phase 1 step 1 → Coder (git worktree A), Phase 1 step 2 → Tester (worktree B), etc.
Output
For Phase 1 (parallel):
# Handoff 1: Conductor → Coder (worktree A)
files you may edit:
- Blaze.LlmGateway.Infrastructure/Providers/GeminiProvider.cs (create)
files other parallel tasks own:
- Blaze.LlmGateway.Tests/Providers/GeminiProviderTests.cs (Tester)
- Blaze.LlmGateway.AppHost/Program.cs (Infra, Phase 2)
# Handoff 2: Conductor → Tester (worktree B)
files you may edit:
- Blaze.LlmGateway.Tests/Providers/GeminiProviderTests.cs (create)
files other parallel tasks own:
- Blaze.LlmGateway.Infrastructure/Providers/GeminiProvider.cs (Coder)
- Blaze.LlmGateway.AppHost/Program.cs (Infra, Phase 2)
Both execute in parallel. When done, Phase 2 starts (Infra depends on both).
Key invariants
- No file overlap within a phase (verified automatically).
- Dependencies explicit (serial phase → parallel phases → serial phase, etc.).
- Each agent owns an exclusive worktree (via
claude-devfleet). - Quality gate applies to every parallel merge (all must pass
-warnaserror+ 95% coverage).
See also
team-builder— decompose tasks into parallel streams (manual).claude-devfleet— Git worktree isolation (execution).quality-gate— validate parallel merges before advancing phases.
Related Skills
imabusyman/write-a-prd
development
VerifiedTrustedCommunity
Generate a Product Requirements Document from a task description, user intent, or PRD outline. Structure the PRD with sections: Overview, Problem Statement, Goals, Scope, Features, Acceptance Criteria, Metrics. Use this when the Planner or Orchestrator needs to formalize requirements before decomposing into implementation steps.
SKILL.mdUpdated Apr 25, 2026
imabusyman/team-builder
development
VerifiedTrustedCommunity
Compose parallel teams of specialized agents for a multi-faceted task. Map subtasks to agent roles, balance workload, and validate team composition. Use this when breaking a task into parallel streams that require different expertise (Coder, Tester, Infra, etc.).
SKILL.mdUpdated Apr 25, 2026
imabusyman/subagent-driven-development
development
VerifiedTrustedCommunity
Delegate implementation work to specialized subagent instances, each inheriting a task scope and constraints from the parent. Emit structured handoffs, monitor completion signals, aggregate results. Use this in the Orchestrator parallel path when spawning independent Coder/Tester/Infra subagents from a single coordinator.
SKILL.mdUpdated Apr 25, 2026
imabusyman/reasoning
testing
VerifiedTrustedCommunity
Maintain the append-only reasoning log and write handoff envelopes for every squad delegation. Use this when the Conductor delegates to a specialist or when a specialist records a non-trivial decision.
SKILL.mdUpdated Apr 25, 2026