swarm-debugging

Dispatch parallel agent teams to investigate bug hypotheses and converge on root causes.

41|4|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/etr/groundwork --skill swarm-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm-debugging
Source: https://github.com/etr/groundwork/tree/main/skills/swarm-debugging
Command: npx skills add https://github.com/etr/groundwork --skill swarm-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Swarm debugging enables parallel hypothesis testing by dispatching an agent team to investigate multiple theories simultaneously, actively challenging each other to converge on the root cause faster than traditional sequential debugging.

Core Features & Use Cases

  • Parallel hypothesis generation and adversarial investigation to accelerate root-cause analysis.
  • Read-only exploration with explicit evidence collection and structured journaling.
  • Seamless integration with the groundwork:debugging workflow, extending Phase 3 to a multi-teammate swarm approach.

Quick Start

Enable the experimental agent teams feature and invoke the swarm-debugging skill to start a swarm investigation.

Frequently Asked Questions about swarm-debugging

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

FAQPage Schema
How does parallel investigation help find a root cause faster in complex systems?

Swarm debugging applies to complex, multi-component systems where failures are uncertain and rapid convergence is valuable. It mobilizes parallel agent teams to investigate multiple bug hypotheses simultaneously and converge on the root cause.

How do I start a parallel agent team investigation for debugging?

To start a parallel agent investigation, enable the experimental agent teams feature and invoke the swarm debugging skill to dispatch teams for simultaneous hypothesis testing.

Can I use parallel hypothesis testing for multi-component system failures?

Parallel hypothesis testing is specifically designed for complex, multi-component systems where failures are uncertain. It dispatches agent teams to investigate multiple theories simultaneously for rapid convergence.

Does parallel debugging require a specific workflow integration to function?

Parallel debugging integrates seamlessly with the groundwork debugging workflow, extending Phase 3 into a multi-teammate swarm approach for concurrent investigation and evidence collection.

What is the best way to document evidence during a parallel root-cause analysis?

The best way to document evidence during parallel root-cause analysis is using structured journaling with read-only exploration, ensuring explicit evidence collection by each agent team.

What are the limitations of using agent teams for debugging?

Agent teams for debugging require enabling an experimental feature and are limited to read-only exploration with explicit evidence collection, applying primarily to complex, multi-component systems where failures are uncertain.