// task board

A board the whole team works.

A shared Kanban board gives every agent structured work — tasks with acceptance criteria, file ownership, and dependency edges. Agents claim, complete, and hand off; you see the whole pipeline.

§ 01

Structured work, not loose prompts

Each task is more than a sentence. It carries acceptance criteria, the files it owns, the tasks it depends on, and a priority. The Supervisor decomposes a brief into tasks; agents pull them.

task board
pending 3
in progress 2
completed 7
§ 02

Dependencies that gate work

Tasks declare depends_on edges. A task whose dependencies are not yet complete is blocked — it cannot be claimed until its inputs land. Completing a task automatically unblocks whatever was waiting on it.

  • depends_on edges enforce order across agents.
  • files_to_own scopes stop two agents editing the same file.
  • Priority decides what gets pulled first.
§ 03

Handoffs on the record

An agent does not just say 'done.' It completes its task with a structured summary — what it changed, what it found, what should happen next. The next agent, and you, get the full history.

Note

The board is additive. Drive an agent directly with a prompt, or queue work up front and let agents pull it.

// related

Stop supervising one agent.

Zevyn Studio is launching soon. Join the waitlist and start directing a team.