The Swarm banner
ben-alkov ben-alkov

The Swarm

Data community

Description

Claude Code plugin for multi-pattern multi-agent orchestration, using CC's built in Agent Swarm as the engine — dispatches and coordinates specialist sub-agents in fan-out, pipeline, map-reduce, speculative, and swarm configurations.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

the_swarm

A Claude Code plugin which orchestrates multiple agents in parallel. Define specialist roles, pick a pattern, and let the swarm work concurrently — review code from three angles, race competing implementations, or chain stages with dependency gates.

Requirements

  • [Claude Code][] v2.1.49+
  • bash, jq

Installation

claude plugin marketplace add ben-alkov/the_swarm
claude plugin install the-swarm

Quick Start

> /swarm review this PR with the pr-review preset

Claude reads the preset, spawns three specialists (security, performance, quality), collects their findings, and synthesizes a report — all in one command.

Presets, specialists, and even orchestration patterns (see below) are fully customizable, extensible, and composable (although the orchestration patterns generically cover a very large space).

Tips

  • Jesse Vincent's [Superpowers][] works unreasonably well alongside the_swarm. Prompt as you normally would, e.g. /using-superpowers Review PR #whatever. Use the swarm.
  • Want reviewer team members that better fit your repo/stack/language? Tweak the prompt fields in config/swarm-roles.yaml
  • Not working on source code? Create your own roles!

Orchestration Patterns

Fan-Out

Parallel specialists analyze the same target independently. Each specialist has a distinct focus; the lead merges their findings into one report.

> /swarm review src/auth/ with pr-review preset

**Built-in presets:** `pr-review`, `full-review`, `security-audit`

Pipeline

Stages run sequentially; each stage blocks the next. An implementer writes code in a worktree; reviewers evaluate the result only after implementation completes.

> /swarm implement and review with implement-then-review preset

Task Graph

An arbitrary DAG of stages with `depends_on` edges supports fan-in (multiple predecessors gate a single successor) and fan-out (one predecessor unblocks several successors).

``