dispatching-parallel-agents

Dispatches concurrent subagents to fix independent test failures across separate problem domains.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/Pega88/agy-superpowers --skill dispatching-parallel-agents-pega88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatching-parallel-agents
Source: https://github.com/Pega88/agy-superpowers/tree/main/.agents/plugins/superpowers/skills/dispatching-parallel-agents
Command: npx skills add https://github.com/Pega88/agy-superpowers --skill dispatching-parallel-agents-pega88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Investigating multiple unrelated failures sequentially wastes time when each problem domain is independent. This Skill coordinates parallel background subagents so each failure gets investigated and fixed concurrently without shared context or interference. ## Core Features & Use Cases - Independent Domain Identification: Groups failures by subsystem to determine which can be worked on in parallel versus sequentially. - Focused Agent Prompts: Provides a structure for self-contained agent prompts with specific scope, constraints, and expected output. - Parallel Dispatch Pattern: Issues multiple invoke_subagent calls in a single response so agents run 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 test file, then review summaries, check for conflicts, and run the full suite to integrate the fixes. ## Quick Start Ask the agent to dispatch one parallel subagent per failing test file, each with a focused prompt describing the failures, constraints, and expected summary output.

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 subagents in parallel?

Issue all subagent dispatch calls in the same response so they execute concurrently. Placing one dispatch per response forces sequential execution instead of parallel.

How to fix multiple failing test files at once?

Group failures by independent problem domain, then dispatch one focused agent per test file with the error messages, constraints, and expected output. Review each summary and run the full suite to verify the fixes integrate cleanly.

When should I not use parallel agents for debugging?

Avoid parallel dispatch when failures are related, when understanding requires full system context, during exploratory debugging, or when agents would share state such as editing the same files.

What makes a good subagent prompt for fixing tests?

A good prompt is focused on one problem domain, self-contained with pasted error messages and test names, explicit about constraints like not changing production code, and specific about the expected output summary.

Why do parallel agents conflict with each other?

Conflicts happen when agents share state, such as editing the same files or using the same resources. Prevent this by assigning each agent an isolated scope and verifying no overlapping changes during integration review.