dispatching-parallel-agents

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

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/Avistian/nba --skill dispatching-parallel-agents-avistian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dispatching-parallel-agents
Source: https://github.com/Avistian/nba/tree/main/.cursor/skills/dispatching-parallel-agents
Command: npx skills add https://github.com/Avistian/nba --skill dispatching-parallel-agents-avistian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Investigating multiple unrelated failures sequentially wastes time when each problem domain is independent. This Skill provides a decision framework and prompt patterns for dispatching one focused agent per independent problem so investigations run concurrently without interference. ## Core Features & Use Cases - Independence Decision Framework: A flowchart and criteria to determine whether failures are independent enough for parallel dispatch or require sequential investigation. - Focused Agent Prompt Structure: Templates for writing self-contained agent tasks with specific scope, constraints, and expected output summaries. - Integration and Verification Workflow: Steps to review agent summaries, detect conflicting edits, and run the full test suite after parallel fixes. - Use Case: After a refactoring leaves 6 failing tests across 3 files (abort logic, batch completion, race conditions), dispatch three agents in parallel—one per file—then integrate their independent fixes with zero conflicts. ## Quick Start Ask the AI to dispatch one parallel agent per failing test file, giving each agent the file name, the failing test names, and a constraint not to touch other code.

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 test file, failing test names, and constraints. Each agent investigates concurrently, and you integrate their fixes afterward.

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

Use parallel agents when failures are independent—different test files, subsystems, or root causes 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 agent prompt for parallel debugging?▼

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.

How do I verify fixes from multiple parallel agents don't conflict?▼

Review 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.

What are the limitations of dispatching parallel debugging agents?▼

Parallel dispatch fails when failures share root causes, when exploratory debugging is needed before domains are known, or when agents share state like editing the same files. In those cases, investigate sequentially with a single agent first.