dispatching-parallel-agents

Dispatches concurrent agents to investigate independent test failures across separate problem domains.

Updated May 18, 2026
One-click install
npx skills add https://github.com/fts-pro/FTS-MMIS-AFRIKA --skill dispatching-parallel-agents-fts-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dispatching-parallel-agents
Source: https://github.com/fts-pro/FTS-MMIS-AFRIKA/tree/main/.agent/skills/dispatching-parallel-agents
Command: npx skills add https://github.com/fts-pro/FTS-MMIS-AFRIKA --skill dispatching-parallel-agents-fts-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple unrelated test failures or subsystem bugs appear at once, investigating them sequentially wastes time and bloats your working context. This Skill provides a structured pattern for splitting independent problems into focused agent tasks that run concurrently. ## Core Features & Use Cases - Independence Decision Framework: A decision flowchart and criteria to determine whether failures are independent enough for parallel dispatch or require sequential investigation. - Agent Prompt Structure: A template for writing focused, self-contained agent prompts with specific scope, constraints, and expected output. - Integration & Verification Workflow: Steps for reviewing agent summaries, checking for conflicting edits, and running the full test suite after parallel fixes. - Use Case: After a major refactoring leaves 6 failures across 3 test files (abort logic, batch completion, race conditions), dispatch one agent per file, then integrate the three independent fixes 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 its assigned 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 debugging sequentially?▼

Use parallel dispatch when you have two or more independent failures with different root causes, no shared state, and no sequential dependencies. If fixing one failure might fix others, investigate them together first instead.

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

A good agent prompt is focused on one problem domain, self-contained with all needed context such as error messages and test names, and specific about constraints and expected output. Avoid vague instructions like "fix the tests" or prompts without context.

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 cause is unknown, or when agents would share state such as editing the same files.

How do I verify fixes from multiple parallel agents do not conflict?▼

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