The kanban board

The kanban board — the Spec board, in the app — holds every ticket a workflow knows about, one card each, in a column for where it stands. It's where you choose what the next run works on, and where a ticket that needs you waits.

I Open the board

Click the kanban icon next to the workflow's name in the dashboard header. Two counts sit on the icon: a red one in its bottom-left corner for the tickets in Attention, and one in its bottom-right corner for the work still in flight — Backlog, Queue, Processing and Merged together.

✦✦✦✦

II The columns

• Backlog — tickets parked for later. A run doesn't take them.
• Queue — tickets the next Start runs, top to bottom.
• Processing — the ticket a run is working on now.
• Merged — the work is finished on your computer, but your remote's main branch doesn't have it yet: a pull request is open, or a local merge hasn't been pushed.
• Attention — a ticket that needs a decision from you: a stage failed it, a pull request was closed without merging, or triage asked a person to decide.
• Done — the work has reached your remote's main branch, or a run finished it cleanly.

During a multi-ticket run, cards move as each stage finishes, so you can watch tickets land one by one.

III Where new tickets land

• When the queue is empty, the first new ticket goes to Queue and the rest to Backlog, so how much the next run takes on is your decision.
• When the queue already has tickets, every new one goes to Backlog, so a scan never widens the batch you lined up.
• Scanning again keeps your sorting: a ticket already on the board stays in its column and place.
• Under 24/7 development there's nobody to promote cards, so everything a scan finds goes straight to Queue.

The Execution Console says where each new ticket went.

IV Move and order cards

• Drag a card onto Queue to run it next, or onto Backlog to park it. Cards in Backlog, Queue, Attention and Done can be picked up; those in Processing and Merged can't, because something is still coming for them.
• Drag within Queue to set the run order — the top card runs first.
• A ticket can depend on another. The board won't put it ahead of the ticket it depends on: the drop is refused with a banner naming the dependency.
• The arrows at the top-right of a column sort what you see by ticket key, priority, or when tickets were updated or created; pick one again to flip its direction. Sorting changes only the view — the run order stays as you dragged it — and Manual order goes back to your own.

V Act on a whole column

Queue, Backlog and Done have an Actions menu at the top while they hold cards:

• Move all to Backlog or Move all to Queue moves every card across at once, keeping their order.
• Clear tickets empties the column. Nothing changes where the tickets came from — no pull request, branch or tracker issue is touched.

Clearing Queue or Backlog means “not now”: the next scan offers the same tickets again. Tick Don't queue them again on the next scan to mean “never” — those tickets stay off the board until they change at the source. Clearing Done asks nothing; it just tidies up finished work.

VI Reading a card

• Where it came from — a ticket from a tracker wears that tracker's colour, with a tab naming it: Jira, Linear, Asana, ClickUp, GitHub or GitLab.
• Test — a black frame with a Test tab marks a stand-in ticket from a test scan, never real work.
• Depends on — a line at the bottom names the tickets this one waits for.
• Paused — a tab on a card in Processing whose run was paused; Resume on the dashboard picks it up.

VII A ticket's details

Click a card to open the ticket. Its tabs show its Details, its Comments and its History; a ticket from a tracker has its key as a link to the original issue. The Actions tab depends on where the ticket came from:

• A ticket from a tracker offers Remove from board. Nothing changes in the tracker; tick Don't queue it again on the next scan to keep it off until it changes there.
• A ticket the workflow wrote — from Specifications or Single Prompt — offers Mark as Done for work finished outside the workflow, Move to Backlog for a ticket in Merged or Done that needs another pass, and Delete ticket file, which removes it for good. You can also add your own notes on its Comments tab.

VIII Attention and recovery

A ticket in Attention carries the reason it stopped, and stays there until you decide — it never runs again on its own, not even under 24/7 development. Open it and use the Recover tab: Return to Queue retries it once you've fixed what the reason names, and some failures offer recovery actions of their own beneath it. Hand off to interactive AI writes a ready-to-paste prompt describing the ticket, the stage that failed and why, so you can finish the change with the assistant you use. You can also drag the card to Queue to retry it, or to Backlog to park it.

IX Run a ticket again

Drag a card from Done back to Queue to have the work done again, then press Start. Start before you scan: a scan rebuilds the board from your trackers, and finished work isn't found again, so the card would go back to Done.