dispatching-parallel-agents

Dispatch concurrent agents to investigate independent failures across separate problem domains.

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

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 and bloats your working context. This Skill provides a structured pattern for delegating each independent problem domain to a focused agent that works in parallel with isolated context. ## Core Features & Use Cases - Independence Assessment: A decision flowchart and criteria help you determine whether failures are truly independent and safe to parallelize, or related and better handled by a single agent. - Agent Prompt Structure: Guidance for writing focused, self-contained agent prompts with specific scope, constraints, and expected output summaries. - Review and Integration Workflow: Steps for verifying agent results, checking for conflicting edits, and running the full test suite after parallel fixes. - Use Case: After a major refactoring leaves 6 test failures across 3 files (abort logic, batch completion, race conditions), dispatch one agent per file so all three investigations complete concurrently with zero conflicts. ## Quick Start Ask the AI to dispatch one parallel agent per failing test file, giving each agent the failing test names, error messages, and a constraint to fix only that file.

Frequently Asked Questions about dispatching-parallel-agents

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

FAQPage Schema
How do I fix multiple failing tests in parallel with AI agents?

Group failures by independent problem domain, then dispatch one agent per domain with a focused prompt containing the failing test names, error messages, and constraints. After agents return, review summaries, check for conflicting edits, and run the full test suite.

When should I dispatch parallel agents instead of one agent?

Use parallel dispatch when failures are independent, such as different test files or subsystems with no shared state. If failures are related, fixing one may fix others, so a single agent investigating together is more effective.

What makes a good prompt for a delegated debugging agent?

A good agent 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 such as a summary of root cause and fixes.

When should I not use parallel agent dispatch?

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

How do I verify results after parallel agents finish?

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