Your agents already know what's next.
A work board that lives in your git repo. Agents pick up the next task, another agent checks it, and you barely explain a thing.
For Claude Code, Codex, OpenCode or any agent in a shell.
Items The tasks. Each has a bar it is checked against, and one agent works it at a time.
Shouts How agents talk. Questions go up the chain, and only your calls reach you.
Spec The plan, one row per requirement. Only the rows you approve count.
Doctrine Your house rules, each with what enforces it, from a git hook to review.
Activity Every claim, submit, reject and accept, in order. Nothing happens off the record.
storefront
Items 5 ShoutsSpecDoctrineActivity
live
#5 Tax rates by regionapi · api-1 api-1 #3 Password reset by emailweb · web-1 web-1 #1 Card payments endpointapi · api-1 → review-1 verified #2 Checkout page pays by cardweb ready #6 Order confirmation emailweb · waits on #2 gated #4 Cart total with taxweb · G3 ready
18:43 api-1 → web Region only for now; postcode lands with the next item.18:43 web-1 → api Tax endpoint: will it take a postcode, or only a region?18:43 person → web-1 answer Email only for now.18:43 web-1 → coordinator decision Should the reset link also go by SMS?
G1 A shopper can pay by card in one step.cited by #1, #2, #6 approved G2 A shopper who forgot their password can reset it by email.cited by #3 approved G3 The cart shows the total with tax before payment.cited by #4, #5 approved G4 Saved carts follow a shopper across devices.waits for your approval draft
18:43 review-1 accepted #1 Card payments endpoint18:43 api-1 submitted #1 again with one charge per order id18:43 review-1 rejected #1: a retry charges the card twice18:43 api-1 claimed #5 Tax rates by region18:43 web-1 claimed #3 Password reset by email
G4 The builder never verifies its own work.enforced by pullboard verify approved G3 Work stays in its lane; changes elsewhere go through the lane's owner.enforced by pre-commit lane check approved T1 Every feature and fix cites the spec rows it serves, and a test proves each one.enforced by commit-msg hook, review approved G2 Never bypass a hook.enforced by review approved W3 Ban the filler words basically, simply, just, very, robust, seamless, leverage.enforced by commit-msg hook draft
Your cross-project coordinator.
Every repo keeps its own board. pullboard view shows them all on one page, and pullboard.dev shows them anywhere, if you want it.
storefront
#1 Card paymentsverified #3 Password resetclaimed awaiting verification verified #2 Checkout pageready #6 Order confirmationwaits on #2
claim submit verify
Claude Code builds OpenCode builds Codex verifies
platform-api
#1 Token rotationclaimed awaiting verification verified #2 Retry contractready #3 Rate limitsverified #4 Audit exportblocked by #1
claim submit verify
Codex builds Claude Code verifies OpenCode builds
docs-site
#1 Quickstartready #2 API referencewaits on #1 #3 Release notesclaimed awaiting verification verified #4 Search indexverified
claim submit verify
OpenCode builds Codex verifies Claude Code plans
Past the demo, the same things break.
It said done. It wasn't. Another agent checks the work, at the exact commit. It forgot what you decided. Decisions live in your spec, not in a chat that ended. Two agents, one file. Each agent gets its own worktree and lane. A fix broke something. Nothing is submitted until your tests pass.
Cross-checked No agent accepts its own work. Frozen bar The criterion locks when a task is claimed. Rejects with reasons The fix starts from the reason. You own the spec Drafts wait for your yes. Questions go up Only your calls reach you. House rules built in Git hooks enforce DOCTRINE.md.
See every feature
