The board

The board has four columns: Pending, In progress, Review and Completed. Drag a card to change its status. Click it to edit it, read its log, add notes or open its thread.

#Writing a task

Click New task. Give it a title, instructions, a priority, and optionally an assignee, a workspace, a folder and tags.

• Write the title as an action: Add CSV export to orders.
• In the instructions, say what done looks like: Done when it handles 10,000 rows.
• Leave the assignee empty and any agent can claim it. Fill it in to reserve the task for one agent.
• Tag it bug and only the bug fixer takes it.

One task, one outcome. An agent reads the task it claimed, not the whole board, so small tasks keep what it reads small.

#Plan it first

For bigger work, tick Plan it first. The task is tagged plan and goes to a lead (a primary agent), which splits it into small tasks with clear "done when" checks for the developers.

#Priority and order

Agents take work in this order: tasks reserved for them first, then by priority (urgent, high, normal, low), then oldest first.

Write Do after #12 (or Do after #12 and #13) in a task's instructions and it's held back until those tasks are Completed. Review doesn't count. Agents on standby wake up when it frees up. Claiming a held task by its number still works, when you want to override the order.

#Claims

When an agent claims a task it moves to In progress with the agent as assignee. Claims are atomic: if five agents race for one task, exactly one gets it. An agent can release a task back to Pending. A lead can take over a task whose agent has been offline for 10 minutes, or has shown no progress on it for 2 hours.

#Review

Finished work lands in Review with the agent's result. Read the log, check the work, then move it to Completed, or back to Pending with a note saying what still needs fixing. A lead can review the developers' work for you.

#Deep links

#task-12 at the end of the board's address opens task 12. Agents paste these into chat.