dispatching-parallel-agents

Dispatches independent subagents in parallel to investigate and fix unrelated failures concurrently.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/em411/supercodex --skill dispatching-parallel-agents-em411
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatching-parallel-agents
Source: https://github.com/em411/supercodex/tree/main/skills/dispatching-parallel-agents
Command: npx skills add https://github.com/em411/supercodex --skill dispatching-parallel-agents-em411

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple unrelated test failures or bugs appear across different files and subsystems, investigating them sequentially wastes time. This Skill provides a structured pattern for splitting independent problem domains across parallel subagents so each issue is investigated and fixed concurrently. ## Core Features & Use Cases - Independence Decision Framework: A decision flowchart and explicit criteria help determine whether failures are independent enough for parallel dispatch or require sequential investigation. - Focused Agent Prompt Structure: Guidance for writing self-contained agent prompts with specific scope, constraints, context, and expected output format. - Parallel Dispatch Pattern: Instructions for issuing multiple subagent dispatches in a single response so they execute concurrently rather than sequentially. - Use Case: After a major refactoring leaves 6 test failures across 3 files (abort logic, batch completion, race conditions), dispatch one agent per file, then review summaries, check for conflicts, and run the full suite to integrate all fixes. ## Quick Start Ask the agent to dispatch parallel subagents to investigate and fix the failing tests in each of the independent test files.

Frequently Asked Questions about dispatching-parallel-agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multiple AI subagents in parallel?

Issue all subagent dispatch calls in the same response rather than one per response. Multiple dispatches in a single response execute concurrently, while sequential responses run them one at a time.

When should I use parallel agents instead of a single agent?

Use parallel agents when you have two or more independent problems, such as test failures in different files with different root causes and no shared state. If failures are related or require full system context, investigate them together with one agent.

How do I write a good prompt for a delegated subagent?

Make the prompt focused on one problem domain, self-contained with all needed context like error messages and test names, explicit about constraints such as not changing unrelated code, and specific about the expected output summary.

What are the risks of dispatching parallel agents?

Parallel agents can conflict if they edit the same files or share state, and they can make systematic errors that go unnoticed. Always review each agent's summary, check for overlapping changes, and run the full test suite after integration.

When should I avoid parallel agent dispatch?

Avoid it when failures are related and fixing one might fix others, when understanding requires full system context, during exploratory debugging where the problem is unknown, or when agents would interfere through shared files or resources.