LOOPD · THE LOOP, RUNNING

You steer.
They build.
Two gates stay yours.

loopd is a Claude Code plugin that runs a small team of AI agents on your repositories. You describe the work. They plan it, build it and get it reviewed. You promote, and you merge.

/loopd:whats-up2 waiting on you
▸ Needs you
1 ◆ promote task-004 draft → ready
2 ◆ merge PR #42 — criteria 6 ✓ / 0 ✗

The same list sits in AWAITING.md, on the session banner and on the board: /pane beside your session, /loopd:board publish on your phone.

THE LOOP

Five stops. Two of them are yours.

The agents work in their lane. The flow only drops into yours twice: nothing is dispatched until you promote, and nothing reaches main until you merge.

AGENTS
YOU
PR
↺ fix
1/loopd:new-projectScaffold, then the PM refinesPhases, tasks, criteriaStep 1 · ScaffoldDescribe the work in one sentence. loopd scaffolds phases and draft tasks; the project-manager adds acceptance criteria and the questions only you can answer./loopd:new-project · /loopd:answer
2GATE 1You promote draft → readyNothing runs until you doGate 1 · You promoteChange a task’s status from draft to ready. The project-manager never promotes on its own, so nothing is dispatched without your say.status: draft → ready
3/loopd:dispatchAn engineer builds itOwn worktree, opens a PRStep 3 · BuildEach tick picks up one ready task. A software-engineer builds it in its own worktree, reviews its own diff and opens a PR with a ✓/✗ criteria table./loopd:dispatch · every 10m, once, or stop
4reviewIndependent reviewBuilt-in or external code reviewerStep 4 · ReviewRuns at the PR’s current head: your external reviewer if one is configured, otherwise the built-in qa-reviewer. A declined review never counts as a pass.fixes go back · one round per reviewer
5GATE 2You merge the PROne ✗ blocks it, however green CI isGate 2 · You mergeMerge, guided by the PR’s criteria table. A single ✗ blocks it however green CI is. Agents never merge on their own.delegable only via loopd-yolo
✓ Done.
Shipped to main
1 · AGENTS · /loopd:new-project
Scaffold, then the PM refines
Phases, tasks, criteria
2 · YOU · GATE 1
You promote draft → ready
Nothing runs until you do
3 · AGENTS · /loopd:dispatch
An engineer builds it
Own worktree, opens a PR
↺ fix, re-review
4 · AGENTS · review
Independent review
Built-in or external code reviewer
5 · YOU · GATE 2
You merge the PR
One ✗ blocks it, however green CI is
✓ Done. Shipped to main

Review can send a PR back for a fix: one round per reviewer, then it comes to you.

Not every project is code

A kind=research project produces documents in the bundle: no repo, no PR. Its second gate is you approving the deliverable.

The Crew

Project managerRuns the loop: refines drafts, dispatches ready tasks, tracks progress and reports back. Never promotes a task itself.tier: deep Software engineerBuilds a task in its own worktree and opens a PR with a ✓/✗ acceptance-criteria table.tier: deep DevOps engineerTakes the infrastructure, CI and deploy tasks.tier: deep QA reviewerThe built-in independent reviewer. Reviews when no external reviewer is set up, or when it refuses.tier: apex Plan architectCritiques the approach while tasks are refined, before anything gets built.tier: apex Failure analystDiagnoses failing builds. Read-only by instruction.sonnet · high effort CataloguerWhen a project closes, folds its conclusions into the bundle’s knowledge/ folder.runs on /loopd:close-project ExplorerClaude Code’s built-in Explore subagent, for fast codebase searches. Not a loopd agent; loopd only sets its tier.tier: light
INSTALL

From install to your first Pull Request.

Needs Claude Code, git, gh (logged in) and bash. The plugin installs once per machine. Each group of repositories gets its own bundle: a small git repo that holds plans, tasks and notes, never application code.

Two or three people can share one bundle; each project has an owner.

ONCE PER MACHINE
/plugin marketplace add cbmono/loopd
/plugin install loopd@loopd # user scope
/reload-plugins
ONCE PER GROUP OF REPOSITORIES
/loopd:init ~/workspace/<group>/_loopd-<group>
# set org, defaultRepo and reposRoot, then start claude inside the bundle
/loopd:init
/loopd:welcome check
THEN, EVERY TIME
/loopd:new-project add rate limiting to the public API
you promote draft → ready
/loopd:dispatch
you merge the PR
SAFETY RAILS

None of them is decoration.

Independent review

Every PR is cleared by a reviewer with fresh context, never the implementing agent’s own report.

enforced by review-clearance.sh

Exit 0 is the only clearance

Missing, pending, skipped and unreadable checks all refuse. So does a reviewer that declined to review.

enforced by required-checks.sh

Destructive commands are blocked

A hook stops shapes like terraform destroy, force-pushes to protected branches and rm -rf of a repo root.

enforced by deny-destructive.sh

Never deletes on a guess

The worktree pruner only reports, and bundle repair is report-only by default. Stale means ask the human.

enforced by prune-worktrees.sh

The gates can be delegated

Only through the separate loopd-yolo plugin, and only for projects set to autonomy: yolo. Uninstall it and every project on this machine is gated again.

How autonomy works →
Every rail, in the reference →