dispatching-parallel-agents

Dispatch concurrent subagents to investigate independent test failures and bugs in parallel.

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

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 delegating each independent problem domain to a focused subagent so investigations run concurrently. ## Core Features & Use Cases - Independence Assessment: A decision flowchart helps determine whether failures are independent enough for parallel dispatch or require sequential investigation. - Agent Prompt Structure: Guidance for writing focused, self-contained agent prompts with clear scope, constraints, and expected output. - Parallel Dispatch Pattern: Instructions for issuing multiple subagent dispatches in a single response so they execute concurrently. - 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 Dispatch one subagent per failing test file to investigate and fix each independent failure in parallel, then review their summaries and run the full test suite.

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 subagent per domain in the same response so they run concurrently. Each agent gets a focused prompt with the failing test names, error messages, constraints, and an expected summary of root cause and fixes.

When should I use parallel agents instead of sequential debugging?▼

Use parallel agents when failures are independent, such as different test files or subsystems with no shared state. Avoid parallel dispatch when failures are related, when understanding requires full system context, or when agents would edit the same files.

What makes a good subagent prompt for fixing test failures?▼

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 such as a summary of root cause and changes.

How do I make subagents run in parallel instead of sequentially?▼

Issue all subagent dispatch calls in the same response to trigger parallel execution. Dispatching one agent per response results in sequential execution, which loses the time-saving benefit of concurrent investigation.

What should I do after parallel agents return their fixes?▼

Review each agent's summary to understand what changed, check whether agents edited the same code and could conflict, run the full test suite to verify all fixes work together, and spot-check results since agents can make systematic errors.