parallel

Dispatch independent agents to fix multiple failing test files concurrently.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the inefficiency of investigating multiple, unrelated issues sequentially by enabling concurrent investigation and resolution through parallel agent dispatch.

Core Features & Use Cases

  • Parallel Agent Dispatch: Assigns independent tasks to separate agents to work simultaneously.
  • Focused Scope: Each agent focuses on a specific problem domain, reducing cognitive load.
  • Use Case: When multiple test files fail due to distinct root causes, this skill dispatches individual agents to fix each file concurrently, significantly speeding up the debugging process.

Quick Start

Use the parallel skill to fix the failures in agent-tool-abort.test.ts, batch-completion-behavior.test.ts, and tool-approval-race-conditions.test.ts concurrently.

Frequently Asked Questions about parallel

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

FAQPage Schema
How do I debug multiple failing test files concurrently instead of one by one?

You can debug multiple failing test files concurrently by dispatching separate agents to investigate and fix each file simultaneously, significantly reducing total debugging time for independent issues.

What is parallel agent dispatch for task management?

Parallel agent dispatch is a task management technique that assigns independent tasks to separate agents to work simultaneously, optimizing debugging time by resolving distinct subsystem issues concurrently.

When should I run independent tasks concurrently versus sequentially?

You should run independent tasks concurrently when multiple failing test files or broken subsystems do not share state or dependencies, allowing simultaneous investigation without risk of interference.

Can I use parallel task execution for broken subsystems that share dependencies?

Parallel task execution is not suitable for broken subsystems that share state or dependencies. It applies specifically to scenarios with multiple distinct root causes that require independent investigation.

What's the best way to speed up debugging for multiple unrelated test failures?

The best way to speed up debugging for unrelated test failures is to assign each failing test file to a focused agent, reducing cognitive load by parallelizing investigations and fixes simultaneously.

Do I need to isolate test failures before using concurrent agent dispatch?

You need to ensure test failures stem from distinct root causes before using concurrent agent dispatch, as this skill relies on resolving independent issues simultaneously without shared state interference.