Cyboflow rev 00113 · docs Home Features Docs Download Changelog
Docs · 03 · the board & the inbox

Backlog & review.

Two surfaces run the whole show: a board that holds the work, and a queue that holds everything the work needs from you.

01Ideas, epics, tasks

The backlog tracks three kinds of entity, linked by lineage:

  • Ideas — raw input. Yours, typed straight onto the board, or captured by a flow.
  • Epics — the grouping layer Planner adds when an idea is big enough to need one.
  • Tasks — the executable unit. Every task knows its parent epic and originating idea, so you can always trace a diff back to the idea that caused it.

Flows read from and write to this same board — there are no side files or parallel to-do lists. What Planner produces is exactly what Sprint consumes.

02Board stages

The board keeps stages deliberately few:

IdeaRaw input captured — not yet planned.
Ready for developmentApproved and queued. Planner drops approved tasks here; Sprint picks them up.
DoneMerged & archived. Merging a sprint moves its tasks here automatically.

When an idea’s plan is approved, the idea itself retires from the board (internally, Decomposed) — its tasks are the live representation from then on. No zombie cards.

03Working the board

  • Open it from the Task backlog item in the left rail.
  • Switch between Kanban and List views; the board spans all your projects, with a project filter.
  • Add work by hand with New Task, move cards between stages, and archive or delete what you’re done with.

04The review queue

Human review in the left rail — with a live pending count — is the one inbox for every running agent across every project. Cyboflow pauses Claude when it needs to take an action; the request lands here, and the agent waits for your answer. Four kinds of item arrive:

PermissionBlocking. An agent wants to run a tool or command your permission mode doesn’t auto-allow. Approve or deny in place.
DecisionBlocking. The agent hit a fork it won’t take alone — pick an option and it continues.
Human taskBlocking. Something only you can do — review a diff, flip a setting, test a build.
FindingNon-blocking. An observation worth your attention — a bug spotted, a missing test, a doc gap. Triage these in Insights.
Keyboard j/k move through the queue, y/n decide. You can clear a backed-up queue without touching the mouse.

The point of the queue: you launch the next agent the moment one unblocks, instead of babysitting each run in its own window.