parallel-agents

Dispatch parallel agents to diagnose independent test or subsystem failures.

4|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/rbaumier/skills --skill parallel-agents-rbaumier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-agents
Source: https://github.com/rbaumier/skills/tree/main/parallel-agents
Command: npx skills add https://github.com/rbaumier/skills --skill parallel-agents-rbaumier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work. When you have multiple independent failures (different test files, different subsystems, different bugs), investigating them sequentially wastes time. Each investigation is independent and can happen in parallel.

Core principle: Dispatch one agent per independent problem domain. Let them work concurrently.

Core Features & Use Cases

  • Choose Architecture Pattern: Supervisor is default; Fan-Out/Fan-In and Pipeline as alternatives.
  • Identify Independent Domains: Group failures by what's broken; each domain is independent.
  • Create Focused Agent Tasks: One task per domain with clear goals and constraints.
  • Dispatch in Parallel: Launch all domain tasks concurrently and monitor progress.
  • Track Progress: Use status reports to coordinate and finish when all domains complete.

Quick Start

Dispatch one agent per independent problem domain and run them in parallel.

Frequently Asked Questions about parallel-agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug multiple independent test failures in parallel without sharing context?

To debug independent test failures in parallel, dispatch one isolated agent per failure domain. This concurrent orchestration pattern preserves your main session context while allowing simultaneous diagnosis of unrelated subsystems.

What is the best way to orchestrate parallel agents for simultaneous subsystem diagnosis?

The best way to orchestrate parallel agents is using a Supervisor pattern to dispatch concurrent tasks. This approach manages isolated agents investigating independent bugs concurrently, rather than sequentially wasting time.

Can I use parallel agent dispatching for investigating unrelated bugs sequentially?

Parallel agent dispatching is explicitly designed for independent failures needing simultaneous diagnosis. If bugs or subsystem failures are unrelated, dispatching isolated agents concurrently prevents the wasted time of sequential investigation.

How do I structure focused tasks for parallel agents investigating different domains?

To structure focused tasks, group independent failures by broken subsystem and create one task per domain with clear goals and constraints. This ensures dispatched agents inherit only constructed context, never session history.

When should I not use a parallel agent orchestration pattern for debugging?

You should not use parallel agent orchestration when failures are dependent on shared context or affect the same subsystem. The pattern requires three or more independent problem domains to be effective for simultaneous diagnosis.

Does parallel agent dispatching support Fan-Out/Fan-In and Pipeline architectures?

Parallel agent dispatching supports Supervisor, Fan-Out/Fan-In, and Pipeline orchestration architectures. Supervisor is the default pattern, while the alternatives provide different coordination structures for concurrent task management and status reporting.