fullstack-swarm

PRD to working code.

Drop in prd/current.md, run /ship-prd, and an eight-agent swarm decomposes, designs, implements, and QAs — including browser-driven visual checks for every UI story.

Get Started Meet the swarm

8 specialized subagents Cursor + Claude Code Backend · UI · Fullstack tracks Visual QA built in Typed status machine 8 specialized subagents Cursor + Claude Code Backend · UI · Fullstack tracks Visual QA built in Typed status machine

agent_trace · fullstack-swarm

$ /ship-prd
● STORY-001  track:backend
│
├─ PM     project-manager     READY_FOR_ARCH
├─ ARCH   solution-architect  READY_FOR_LLD
├─ TL     tech-lead           READY_FOR_BUILD
├─ DEV    developer           READY_FOR_QA
└─ QA     qa-engineer         DONE

● STORY-002  track:ui
│
├─ UX     ux-designer         READY_FOR_BUILD
├─ FE     frontend-developer  READY_FOR_QA
├─ QA     qa-engineer         READY_FOR_VISUAL_QA
└─ VQA    visual-qa           DONE

Queue score  2/2 stories shipped  passed

Evaluate

One orchestrator.
Eight specialists.

Most agent setups dump everything into one context window. fullstack-swarm keeps a typed status machine in the main session and dispatches one specialized subagent per stage.

Subagents never call each other — every handoff goes through the orchestrator — so you get clear artifacts and a queue you can inspect with /status.

Track-aware routing

backend, ui, and fullstack stories take different paths — UX design and visual QA only where they belong.

Inspectable queue

Every story lives in stories/_queue.json with a status, deps, and history. No black-box loops.

Visual QA gate

UI stories don’t ship on green unit tests alone — a browser-driven visual check is the final gate to DONE.

Flexible techniques

Decompose → design → build → QA.

Compose a full delivery loop from a single PRD — plain-English requirements in, scored artifacts out.

01project-managerREADY_FOR_ARCH
02solution-architectREADY_FOR_LLD
03tech-leadREADY_FOR_BUILD
04ux-designerui / fullstack
05developer / frontendREADY_FOR_QA
06qa-engineerDONE / VISUAL
07visual-qaDONE

The swarm

Specialists, not a monolith.

Each agent runs in its own context with restricted tools, scoped to one job.

Subagent	Tracks	Job
`project-manager`	all	PRD → atomic, track-tagged stories
`solution-architect`	all	HLD + ADRs
`tech-lead`	all	LLD + confirmed track
`ux-designer`	ui, fullstack	UX spec + design tokens
`developer`	backend	Implement + tests under `src/`
`frontend-developer`	ui, fullstack	Implement + tests under `web/`
`qa-engineer`	all	Functional QA report
`visual-qa`	ui, fullstack	Live browser checks + screenshots

Trace, grade, iterate

Ship without leaving your editor.

Works as a plugin for Cursor and Claude Code. On Claude, add the GitHub repo as a marketplace, then install by plugin name. Scaffold once, write a PRD, then drive the pipeline with slash commands.

install · Cursor

git clone git@github.com:mandarzope/fullstack-swarm.git
mkdir -p ~/.cursor/plugins/local
ln -s "$(pwd)/fullstack-swarm" ~/.cursor/plugins/local/fullstack-swarm

install · Claude Code (marketplace)

claude plugin marketplace add mandarzope/fullstack-swarm
claude plugin install fullstack-swarm

# Use the plugin name fullstack-swarm,
# not the repo path.

ship · agent

/swarm-init
# write prd/current.md
/ship-prd
/status
/next

Commands

Four verbs. Full pipeline.

`/swarm-init`

Scaffold dirs, agents, and orchestrator rules into the target repo.

`/ship-prd`

Decompose prd/current.md and run the autonomous pipeline.

`/status`

Read-only queue table plus the exact next dispatch.

`/next`

Keep dispatching eligible stories until DONE, BLOCKED, or stuck.

Any editor. Any track.

Cursor. Claude Code. Your repo.

Plug fullstack-swarm into the tools you already ship with — no rewrite required.

Cursor
Claude Code
GitHub
backend
ui
fullstack

Ah yes, FAQs.

Questions, answered.

What is fullstack-swarm?

An eight-agent software delivery swarm packaged as a Cursor / Claude Code plugin. It turns a PRD into working backend and UI code through a typed status machine and specialized subagents.

How is this different from one big coding agent?

Subagents cannot dispatch each other. Every handoff routes through the orchestrator, producing inspectable artifacts (stories/, design/, src/, web/, tests/) instead of an opaque chat transcript.

How do I install with Claude Code marketplace?

Add the GitHub repo as a marketplace, then install by plugin name:

claude plugin marketplace add mandarzope/fullstack-swarm
claude plugin install fullstack-swarm

Use fullstack-swarm (the plugin name), not the repo path.

Do I need both Cursor and Claude Code?

No. Install whichever you use. The same agents, commands, and scaffold work in both environments.

What are tracks?

backend skips UX and visual QA. ui and fullstack go through UX design and browser-driven visual QA before DONE.

Can I resume after a stop?

Yes. Run /status to see the queue, then /next to continue dispatching from where the pipeline left off.

Ready when you are

Start shipping.

Clone the plugin, run /swarm-init, drop a PRD, and let the swarm take it from there.

Get Started View install