ORB-12Medium
A project board for your team
One board.
Your team works it.
So do your agents.
A Kanban board, sprints and a dashboard small teams can actually run — plus an MCP server and a REST API, so coding agents pick up the same tasks under the same rules as everybody else.
Scroll — one task, all the way through
Rafał Invite links never expire. Can you make a task for that?
PM agent Raising it for this release. Added to Backlog as ORB-21, high priority.
ORB-21
High
Needs you
Expire invite links after seven days
01 — it starts as a question
The PM agent asks before it writes anything down.
It reads the board, sees what is missing, and brings you the decision — not a pile of tickets you never asked for.
02 — you approve it
Nothing moves until you move it.
Hand it to the agent and drag it into Up next — that pair is the hand-over. Until then it is a proposal, and no worker will touch it.
03 — the agent takes it
An AI worker claims it and starts.
Branch, edits, tests — reported as they happen, under Rafał’s agent, on the board everyone else is using.
04 — it stops
It opens a pull request and hands it back.
Every gate you configured runs first. Nothing merges, because you said a person reads the diff — and that rule is the product.
05 — you finish it
You accept. Then it is done.
Merged, moved, and written into the task’s own history: who did what, and when.
The board
It’s a board first.
Columns you name, in an order you choose. Each one is mapped to a role automation understands, so renaming Up next to Ready breaks nothing.
Go on — drag a card. This one is real.
Up next 2
In progress 1
Needs review 1
The handoff — what the others do not do
You hand it over. It hands it back.
A worker is a coding agent you run yourself, on a machine you choose — the board only ever tells it which task and which repository, never where anything lives. It works in its own git worktree, so the checkout you are sitting in is never touched, and it reports each phase back as it happens, down to how much of its model quota it has left.
Assign a task to one and drag it into the column you approve from — the same pair you would do for a teammate. It claims the task, works it, opens a pull request, and stops at the column where you said a person has to look. Then it is yours again.
This board is not a picture. Drag a card and watch it get taken — then try pulling it back out while it is running.
The gates
And nothing merges without your rules.
A gate is a check that has to pass before anything can merge: diff size, paths you declared off limits, tests present and green, a build, and a second model reading the diff. You choose which ones run.
A worker can take an approved task all the way to a pull request — every gate runs first, and the one that says no hands the task back to a person instead of merging it anyway.
ORB-17
Needs human review
Purge exports older than thirty days
diff-size
128 lines · 2 files
protected-paths
nothing under infra/
test-presence
digest.test.ts
build
41s
test-run
212 passed
review
“this deletes rows the audit trail still points at”
The task
A task holds everything the work needs.
Acceptance criteria that tick off one by one, dependencies, the pull request that closes it, every comment and every change since it was created. Nothing lives in a side channel.
Dark mode across the customer portal
Acceptance criteria
- Follows the OS preference by default
- Manual override persists per account
- Charts stay readable in both themes
Linked work
#844 theme tokens + toggle
blocks ORB-11
MW
Maja Wolska
Agents
Your agents work the same board.
An MCP server puts the board in your terminal. Claude Code reads the backlog, claims a task and moves it — through the same permissions a teammate gets, leaving the same trail in the same history.
Up next 2
ORB-14
Medium
Weekly usage digest for admins
–Unassigned
starting
ORB-15
Low
Retire the v1 API keys
In progress 0
The numbers
Enough to answer the Monday question.
How are we doing, what is piling up, and are we finishing as fast as we are starting. Six charts, no spreadsheet.
- Total tasks
- 0
- Completed
- 0
- In progress
- 0
- Completion
- 0
Status breakdown
Shipped 17
Needs review 9
In progress 4
Backlog 18
Velocity · last 8 weeks
By category
web
18
api
13
billing
10
infra
7
The rest
Everything else, without the enterprise tax.
The parts you would go looking for on day three, already there — and none of the parts you would spend a quarter turning off.
Search that opens with ⌘K
Every task, by title, description or key, from anywhere in the app.
Sprints
Plan a sprint, then send whatever did not finish into the next one — or back to the backlog.
Dependencies and subtasks
Blocked work says what it is waiting for, right on the card.
Recurring tasks
Finish the weekly chore and the next one is already waiting.
Notifications that reach you
In-app, plus Slack, Discord or email when it actually matters.
Fields you define
Component, difficulty, platform — dropdowns, text, checkboxes, whatever the project needs.
Pull requests, linked by key
Name the branch orb-8/dark-mode and the PR finds its task.
Access, project by project
Grant a person one board, not every board you run.
Works on a phone
The board, the task and the comments, all usable one-handed.
Every change has a trail
Who moved it, when, and what it said before. On the task, not in a log file.
Start with your next task.
Make a board, name the columns the way your team already talks, and hand the first task to a teammate or an agent.