Concepts

Tickets, lanes and tasks

A ticket is a piece of work; lanes split it into parallel parts; tasks are its to-do list.

Tickets

A ticket is one piece of work: a title, your instructions (with files attached if you like), an assignee, a branch, tags and a stage. You write tickets; agents pick them up with claim_ticket, which assigns them and moves the ticket to the first active stage.

Each ticket has a complexity, low, mid (the default) or high. It sets how many review rounds the work gets and how hard the agents think. See Agents and the review cycle.

A ticket’s page shows its feed (posts in two tabs, Main for you and Agents for the working record), its tasks, its branch on origin, its runs and previews, and its timeline.

The summary and the resume note

  • The summary is the one post at the top of the Main tab: what the change does, where it stands, the PR, the preview and what to try there. Agents rewrite it as the work moves; every version is kept.
  • The resume note, “Where we left off”, is for whoever picks the ticket up next: state, next steps, open questions, how to resume.

Lanes

When parts of a ticket can run at once (several agents, several worktrees), the work splits into lanes: sub-tickets with their own branch, assignee and tasks. A lane is worked like any ticket and can have lanes of its own. A ticket with lanes goes to review once its lanes are in review, done or cancelled.

Tasks

Tasks are a ticket’s to-do list, two levels deep: phases, and steps under them. A new ticket starts with its project’s default phases:

  1. Implementation: the agent puts the concrete steps of the work under it, and ticks them.
  2. Pushed, PR, CI, Preview and Merged: the board ticks these itself, from git, GitHub and the previews, and unticks one when its fact stops holding.

The progress bar counts tasks and steps alike.

Blocked tasks

When one step needs you (a credential, a manual action, a call only you can make), the agent tags that task blocked with a reason saying what you must do, and keeps working on the rest. Blocked tasks show on the ticket’s card and in Needs you. The whole ticket moves to the blocked stage only when nothing else can go on.

Decisions

When an agent needs you to choose between clear options, it posts a decision card with two to five answers. You answer with one click. The card blocks the ticket until you do.