swarm

Orchestrates parallel subagent exploration, independent reviewer validation, and critic challenge for code tasks.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/pandejesal/drone-nav-sar --skill swarm-pandejesal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm
Source: https://github.com/pandejesal/drone-nav-sar/tree/main/.swarm/bundled-skills/swarm
Command: npx skills add https://github.com/pandejesal/drone-nav-sar --skill swarm-pandejesal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Complex coding and review tasks often ship with undetected defects because a single agent both implements and verifies its own work. This Skill enforces a rigorous multi-agent workflow that separates candidate generation from validation, so findings and code changes are independently reviewed and challenged before completion is declared. ## Core Features & Use Cases - Parallel Exploration and Mapping: Fan out explorer subagents across disjoint scopes for repository mapping, security review, dependency review, and test analysis. - Independent Reviewer and Critic Gates: Validate candidate findings with skeptical reviewer subagents, then challenge confirmed findings with a separate critic before synthesis. - Mandatory Implementation Closeout Gate: Any task editing code, tests, docs, or package metadata must pass objective validation, an independent implementation reviewer, and a final critic on the latest diff before completion. - Use Case: When refactoring an authentication module, the agent parallelizes subsystem investigation, has a reviewer verify each candidate issue as CONFIRMED or DISPROVED, and blocks completion until a critic approves the final diff and evidence. ## Quick Start Enable swarm mode for this session and use parallel explorer, reviewer, and critic subagents for my next complex coding task.

Frequently Asked Questions about swarm

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

FAQPage Schema
How do I use parallel subagents for code review?

Spawn explorer subagents across disjoint scopes to map the codebase and generate candidate findings, then send those candidates to independent reviewer subagents for validation. Use critic subagents only after reviewer confirmation to challenge high-impact findings in small batches.

What is the difference between explorer, reviewer, and critic subagents?

Explorers are broad, fast candidate generators that map scopes and flag suspicious code. Reviewers independently validate candidates and classify them as CONFIRMED, DISPROVED, UNVERIFIED, or PRE_EXISTING. Critics challenge reviewer-confirmed findings, looking for overclaimed severity and weak evidence.

When is the implementation closeout gate required?

The gate is required for any task that edits code, tests, docs, package metadata, release notes, or skill files. Completion requires objective validation, an independent implementation reviewer approval, and a separate critic approval on the latest diff, with all verdicts recorded in durable artifacts.

Can I skip reviewer validation for low-risk tasks?

Read-only or answer-only work like explaining existing code or summarizing an already-reviewed diff can use a lighter path when evidence is strong. However, required workflow steps can never be skipped due to time pressure, token cost, or perceived repository simplicity.

What happens if code is edited after reviewer approval?

Any edit after reviewer or critic approval invalidates that approval. The affected reviewer or critic gate must be re-run on the new diff and evidence before final synthesis, and the latest edit must be older than the latest approvals.