dispatching-parallel-agents

Dispatches independent tasks to parallel subagents with focused prompts and isolated context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple unrelated failures or tasks exist (different test files, subsystems, or bugs), investigating them sequentially wastes time and pollutes your working context. This Skill provides a structured pattern for delegating independent problem domains to parallel subagents with precisely crafted, self-contained instructions. ## Core Features & Use Cases - Parallel Dispatch Pattern: Issue multiple agent dispatches in a single response so they run concurrently in the background, then retrieve results with get_subagent_result. - Focused Prompt Structure: Each agent receives a specific scope, clear goal, explicit constraints, and an expected output format so it stays on task without inheriting session context. - Decision Guidance: A flowchart and explicit use/don't-use criteria help decide when failures are independent enough for parallel dispatch versus sequential investigation. - Use Case: After a 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 fixes. ## Quick Start Ask the AI 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 Agent dispatch calls in the same response so they execute concurrently. Agents run in the background by default, and you retrieve results later with get_subagent_result using the agent ID and wait option.

When should I dispatch parallel agents instead of investigating sequentially?

Use parallel dispatch when failures are independent, such as different test files or subsystems with different root causes and no shared state. If fixing one failure might fix others, investigate them together first.

What makes a good subagent prompt for fixing tests?

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

When should I not use parallel agent dispatch?

Avoid it when failures are related, when understanding requires full system context, during exploratory debugging where the problem is unknown, or when agents would share state like editing the same files.

How do I verify results after parallel agents finish?

Read each agent's summary, check whether agents edited the same code and conflict, run the full test suite to confirm fixes work together, and spot check changes since agents can make systematic errors.