prompt engineering peaked at "bro, wtf"

Every agent needs a bro.

bro is a hook system that organizes and orchestrates tasks for any agent. Install the plugin — Claude, Codex or Devin calls bro and stops forgetting, faking "done", and wandering off.

$ /plugin marketplace add ThePlenkov/bro
$ /plugin install bro@bro
your agent · ~/app · bro plugin on
>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 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 act wait --merge)
└exit_gate=OK — merged
●Now it is done. For real this time.

real commands, dramatized agents.

How it works

  1. pluginskills + hooks

    lives inside your agent. rehydrates context on start, blocks the stop while work is unfinished.

  2. broone CLI

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

  3. connectorsyour systems

    beads, GitHub, GitLab — and whatever you plug in next — behind the same facades.

Not another orchestrator

No swarm. No extra sessions. No token bonfire. Your agent keeps its own session — bro hooks into its lifecycle and keeps it honest. Gates, not loops.

The whole vocabulary

bro wtf
log the frustration. verbatim. with receipts.
bro drill
go deeper. you must come back with a result.
bro act
done? prove it. threads, checks, mergeable.
bro debt
merged PRs still owe you. bro collects.
bro next
what now? bro picks. you ship.
bro loop
fine, bro drives. you review.