---
title: "swarm-forge"
description: "Disciplined tmux-based agent orchestration: pick a pack of specialist agents, give each its own git worktree, and drive them from a local web cockpit."
canonical: https://agentpluginsdirectory.com/plugins/swarm-forge
last-updated: 2026-10-08
---

# swarm-forge
Disciplined tmux-based agent orchestration: pick a pack of specialist agents, give each its own git worktree, and drive them from a local web cockpit.
- Slug: swarm-forge
- Publisher: Robert C. Martin
- Repository: https://github.com/pproenca/dot-plugins
- Manifest: plugins/swarm-forge/plugin.json
- Version: 0.16.9
- Category (editorial): agent-tooling
- Skills: 3 (swarm-forge-cockpit, swarm-forge-handoffs, swarm-forge)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-08-23
- Repository last pushed: 2026-09-06
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/swarm-forge
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What swarm-forge does, in the publisher's words

> ## Packaged as an Agent Plugin > > This is unclebob/swarm-forge repackaged to the > Agent Plugins Specification v1.0.0. Install and startup differ from the upstream > instructions below. > > Upstream ships each workflow as a separate git branch and expects you to extract a branch > tarball over your project, after which./swarm downloads the engine from GitHub. A > plugin cannot be several branches, so the four rosters are vendored here as data under > packs/ and the download is replaced by an offline install: > > bash > skills/swarm-forge/scripts/install_pack.sh > cd &&./swarm > > > The install produces the same project layout upstream's bootstrap produces, the pack > payload, the engine at swarmforge/scripts/, close-swarm, and a./swarm: plus the > Acceptance Pipeline tooling pre-seeded under.swarmforge/, which upstream clones from > GitHub on first use.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/pproenca/dot-plugins/HEAD/plugins/swarm-forge/README.md

## Skills

- swarm-forge-cockpit: Operate a running SwarmForge swarm from its web cockpit, start tasks, approve handoffs, answer agent clarifications, read the board and Work Queue, and tear down. Use for "the swarm dashboard", "approve the handoff", "the swarm is stuck", or driving agents already running.
- swarm-forge-handoffs: The SwarmForge handoff protocol: how an agent inside a swarm queues work with swarm_handoff.sh, accepts it with ready_for_next.sh, completes it with done_with_current.sh, and asks a human for clarification. Use when writing role prompts, debugging stalled handoffs, or acting as a role in a swarm.
- swarm-forge: Run a SwarmForge swarm: install a pack of specialist agents into a project, launch them in tmux with one git worktree each, and tear the swarm down. Use for "swarmforge", "start a swarm", "two-pack/four-pack/six-pack", or setting up multi-agent orchestration on a repo.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.