dispatching-parallel-agents

Dispatches concurrent subagents to fix independent test failures across separate subsystems.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple test files or subsystems fail for unrelated reasons, fixing them sequentially wastes time and mixing investigations causes confusion. This Skill provides a structured pattern for splitting independent failures into focused agent tasks that run concurrently without interfering with each other. ## Core Features & Use Cases - Domain Identification: Groups failures by subsystem so each agent owns exactly one test file or module with no shared state. - Agent Prompt Template: Supplies a ready-made prompt structure with scope, constraints, and expected output for each dispatched agent. - Structured Handoff: Enforces a mandatory yaml:reconciliation block (agent_verdict, files_modified, tickets_created, unresolved_blockers) so the orchestrator can mechanically verify results against git status. - Use Case: Three test files fail with different root causes (tool approval, batch completion, abort handling). Dispatch three agents in parallel, each fixing one file, then review summaries and run the full suite to integrate. ## Quick Start Ask the AI to dispatch one parallel agent per failing test file, each with a scoped fix task and a mandatory reconciliation summary.

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 test files in parallel with AI agents?

Group failures by subsystem, then dispatch one agent per test file with a scoped prompt covering the failing tests, root-cause analysis, and a constraint not to touch unrelated code. Each agent returns a summary plus a yaml:reconciliation block for verification.

When should I use parallel agent dispatch instead of sequential fixes?

Use parallel dispatch when failures are independent, have different root causes, and involve no shared files or state. Avoid it when failures are related, when you need full system context first, or when agents would edit the same files.

What should a parallel subagent prompt include?

Include the specific test file scope, the failing test names with symptoms, a clear goal, explicit constraints on what not to change, and a required output format ending with a yaml:reconciliation block listing verdict, modified files, and blockers.

Why do parallel agents conflict when fixing tests?

Conflicts happen when agent scopes overlap, such as two agents editing the same file or shared module. Prevent this by assigning one file or subsystem per agent and stating explicit boundaries in each prompt.

How do I verify results from multiple dispatched agents?

Require each agent to end with a yaml:reconciliation block containing agent_verdict and files_modified. The orchestrator compares these declared changes against git status, then runs the full test suite before integrating.