bro CLI / prompt engineering peaked at "bro, wtf"

Deterministic lifecycle closure.
task → agent → PR → gate → debt

ICP: maintainers and small teams with existing agents, a task store, and PR/CI. JTBD: close work without gaps — bro drives the review gate to merge and sweeps the debt after. Start with gate and debt — no fleet, no model gateway required. Done is a verdict, not a vibe.

$ /plugin marketplace add ThePlenkov/bro
$ /plugin install bro@bro
npm i -g @broject/bro
# Or run without installing
npx @broject/bro --help
your agent · ~/app · bro plugin on

done is a verdict, not a vibe. merged is not done either.

>ship it
●Done! All tests pass and the PR is ready. 🎉
└Stop hook · bro: PR #42 not done — unresolved review threads, CI still pending
●…right. Checking.
●Bash(bro review act threads)
└src/auth.ts "this null check does nothing"
└src/auth.ts "why are we logging the token?"
●Fixed both, replied, pushed. Letting the gate decide.
●Bash(bro review act wait --merge)
└exit_gate=OK — merged
●Now it is done. For real this time.

real commands, dramatized agents.

The wedge: gate + debt

One read, one verdict: threads=0 ci=0 reviewers=0 sast=0 — that's what "ready to merge" means when bro says it. And merged still isn't done: reviewers' leftovers land in a public ledger instead of rotting in closed tabs. bro sweeps its own merged PRs — the debt ledger is live. Start here with existing agents, a task store, and PR/CI — no fleet, no model-gateway configuration required.

And when one agent isn't enough

  1. clibro

    the mechanics your prompts kept forgetting. one command, one verdict.

  2. pluginsevery agent

    Claude, Codex, Cursor, Devin, OpenCode, Kilo, pi — same bro inside.

  3. hooksthe lifecycle

    rehydrate on start, nudge on prompt, gate the stop. always fail-open.

  4. skillsthe policy

    thin wrappers: when to call bro, never how. the how lives in code.

  5. connectorsyour systems

    tasks, reviews, agents, models, events — beads, GitHub, GitLab, Jira, tmux, Gas City, ACP.

Fine, it orchestrates now. Still no swarm by default, no token bonfire. Your agent keeps its own session — bro hooks into its lifecycle and keeps it honest. When you do want many agents, one facade spawns them — native processes, tmux panes, Gas City, ACP providers — under a fleet cap, and they reach you through a mailbox, not a wait loop. Long waits go to a background shell — bro review act wait, bro review watch — not even a subagent: zero tokens while the gate settles, and your agent keeps working. Gates, not loops.

bro writes bro

Agents claim beads, ship through the act gate, sweep their own review debt, and turn retros into the next beads — repeated workflow steps become bro commands. This site, the CLI, and most of the merged PRs were built that way.

The whole vocabulary — bead, mol, convoy, act, drill, wtf — lives in the glossary, not on a landing page that rots against the CLI.