Built for teams that ship with Claude Code

Plan it.
Build it.
Journal it.

Swarm moves your team and its AI agents as one. Every job gets a plan, a branch, a builder and a journal — and everyone knows the moment it moves.

How it works

One job. One plan, one branch, one journal.

Swarm is the handoff between the people who plan and the people (and agents) who build.

01
PM
Plan

Write plan.md in Swarm — goal, steps, files, done-when. Pick a dev and a branch. Send.

02
Dev + Claude Code
Build

The dev gets the branch, the bundle and a ready prompt. Claude Code builds from the plan; the dev tests and reviews.

03
Dev → PM
Journal

dev_journal.md comes back: what was done, skipped, changed and verified. The PM reviews, reopens or marks it done.

Features

Everything the handoff needs. Nothing it doesn't.

Plans in Markdown

Write in a real editor with live preview and autosave, or upload the .md you already have. Every edit is versioned; diff and restore any snapshot.

# Plan

## Steps
1. Add limiter
2. Return 429
Plan
Steps
1. Add limiter
2. Return 429

Branch handoff

Each job names its branch. Devs copy the git commands and go.

$ git checkout -b swarm/JOB-12-…

Live notifications

Sent, started, submitted, done — the right person hears instantly.

Dan submitted JOB-12 for review

Dev journals

What was built, skipped and verified — every job ends with a written record.

In devIn review

state.json for agents

Machine-readable job state, regenerated on every change, shipped in the bundle.

Roles that keep the plan honest

PMs write plans, devs write journals. The plan locks while the dev builds, so nobody codes against a moving target. Admins manage people and projects.

Product

The job page: the whole story of one change.

swarm / kc-cycle / JOB-12
Login rate limitIn review
Dev Journal
1In-memory limiter, 5 / 30 s✅2429 with Retry-After✅3Reset on success✅
Handoff
swarm/JOB-12-login-rate-limit
⬇ Download bundle
Copy Claude Code prompt