From afyapowers
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
How this skill is triggered — by the user, by Claude, or both
Slash command
/afyapowers:dispatching-parallel-agentsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Note:** This skill is for ad-hoc parallel investigation (debugging, test fixing, research). For parallel execution of implementation plan tasks, see the wave execution algorithm in `skills/subagent-driven-development/SKILL.md`.
Note: This skill is for ad-hoc parallel investigation (debugging, test fixing, research). For parallel execution of implementation plan tasks, see the wave execution algorithm in
skills/subagent-driven-development/SKILL.md.
When you have multiple unrelated failures (different test files, different subsystems, different bugs), investigating them sequentially wastes time. Each investigation is independent and can happen in parallel.
Core principle: Dispatch one agent per independent problem domain. Let them work concurrently.
Use when:
Don't use when:
Group failures by what's broken:
Each domain is independent - fixing tool approval doesn't affect abort tests.
Each agent gets:
// In Claude Code / AI environment
Task("Fix agent-tool-abort.test.ts failures")
Task("Fix batch-completion-behavior.test.ts failures")
Task("Fix tool-approval-race-conditions.test.ts failures")
// All three run concurrently
When agents return:
Good agent prompts are:
Too broad: "Fix all the tests" - agent gets lost Specific: "Fix agent-tool-abort.test.ts" - focused scope
No context: "Fix the race condition" - agent doesn't know where Context: Paste the error messages and test names
No constraints: Agent might refactor everything Constraints: "Do NOT change production code" or "Fix tests only"
Vague output: "Fix it" - you don't know what changed Specific: "Return summary of root cause and changes"
Related failures: Fixing one might fix others - investigate together first Need full context: Understanding requires seeing entire system Exploratory debugging: You don't know what's broken yet Shared state: Agents would interfere (editing same files, using same resources)
After agents return:
npx claudepluginhub iclinic/devex-marketplace --plugin afyapowersDispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Delegates independent tasks to parallel subagents, each with isolated context. Use when 3+ test failures or subsystems have unrelated root causes.
Dispatches parallel agents to handle 2+ independent tasks like fixing unrelated test failures in separate files or subsystems without shared state.