A Tasker board. Moving a card to Done is refused until a Manager approves it, the Done column links its rules page, and a card an agent moved says Ana via ci-deploy-token.
Gates
Pick a column. Say what a card needs before it gets in: an approval from a role, an assignee, a description, a label, every subtask done, or a free slot under the WIP limit.
Nobody argues in a thread. The board says no, and says why.
The gates on In progress: at most 3 cards, which is full at 3 of 3, and an assignee, which is met. A move into it is refused: In progress is full (3 of 3).
An agent calls move_task to move a card into Review, and the same gate refuses it: Review needs a description first. The card says Ana via ci-deploy-token.
Agents
Hand an agent a personal token and point it at the MCP server. It moves cards through the same checked path as everyone else, so a gate that stops you stops it.
Read-only tokens read. Write tokens write. A token can never approve its own work, and every card it touches says who and through what.
Docs
Write your definition of done once and link it to the column. It shows up exactly where a move is refused, for the person dragging the card and for the agent that tried.
No wiki to forget. No tab to hunt for.
The project's Docs tab, showing the Definition of done page, linked to the Done column.
What we leave out
Somewhere along the way the tracker became a job of its own, with a team to feed it. We kept the board and cut the theatre.
Estimate in your head. Ship in the board.
The work is done or it is not.
Nobody here is graded on a line going up.
Every gate is in the product. No plan unlocks them.
A card needs a title. The rest is your rule, per column.
Nothing here exists so someone can watch someone else work.