dispatching-parallel-agents

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

1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/stefanfaur/roach-marketplace --skill dispatching-parallel-agents-stefanfaur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dispatching-parallel-agents
Source: https://github.com/stefanfaur/roach-marketplace/tree/main/roach/skills/dispatching-parallel-agents
Command: npx skills add https://github.com/stefanfaur/roach-marketplace --skill dispatching-parallel-agents-stefanfaur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Investigating multiple unrelated failures sequentially wastes time and bloats your context. This Skill provides a structured pattern for delegating independent problems to isolated agents that work concurrently, each with focused scope and self-contained instructions. ## Core Features & Use Cases - Parallel Agent Dispatch: Launch one agent per independent problem domain (e.g., one per failing test file) so investigations run concurrently instead of sequentially. - Agent Type Selection: Match work to the right agent — read-only agents like codebase-locator and codebase-analyzer for investigation, general-purpose agents for read-write fixes. - Prompt Structure Guidance: Craft focused, self-contained agent prompts with clear scope, constraints, and expected output to prevent agents from drifting or over-editing. - Use Case: After a refactoring leaves 6 test failures across 3 files, dispatch 3 agents in parallel — one per file — then review summaries, verify no conflicts, and run the full suite to integrate all fixes. ## Quick Start Ask the assistant to dispatch one parallel agent per failing test file to investigate and fix each failure independently, then review and integrate the results.

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 agents in parallel to fix failing tests?▼

Group failures by independent problem domain, then dispatch one agent per domain with a focused prompt containing the failing test names, error messages, constraints, and expected output. All agents run concurrently, and you review and integrate their fixes afterward.

When should I dispatch parallel agents instead of investigating sequentially?▼

Use parallel dispatch when you have two or more independent problems with no shared state or sequential dependencies, such as different test files failing for different root causes. Avoid it when failures are related or agents would edit the same files.

What makes a good prompt for a dispatched agent?▼

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

Which agent type should I use for read-only codebase investigation?▼

Use purpose-built read-only agents such as codebase-locator to find where things live, codebase-analyzer to understand a component, or codebase-pattern-finder to locate similar implementations. Reserve general-purpose agents for work that must edit files.

What are the risks of running parallel agents on the same codebase?▼

Parallel agents can conflict if they edit the same files or share state. After they return, review each summary, check for overlapping changes, run the full test suite, and spot-check results since agents can make systematic errors.