Donezo logoDonezo Download

Team

How a director splits work, who checks it, and where you watch it happen.

Delegation

A director agent does not do the hands-on work. For each unit it starts a sub-agent and gives it:

Each director can have 4 active sub-agents at once (ORCH_SUBAGENTS_MAX). Past that, it is told to wait for one to finish or to cancel one.

You can delegate by hand as well. On the Team tab, press Delegate a task and fill in Report the result to, Playbook, Title, Brief and Done means. Brief and Done means are required.

The four playbooks

PlaybookWhat it doesWhere
featureBuilds one feature and proves it works on the real interface.Own worktree and branch
bugfixReproduces the bug first, finds the root cause with evidence, then fixes it and checks the same reproduction.Own worktree and branch
refactorRecords current behaviour first, then changes structure in small steps that keep that record the same.Own worktree and branch
investigateAnswers a question with evidence from the code and its history. Read-only.The director's folder

A worktree is a separate copy of your project on its own branch, named orch/<id>. If the director's folder is not a git repository, a sub-agent has no worktree and shares that folder; its card says no worktree.

Once a finished sub-agent's branch is merged into another local branch of the same repository, Donezo removes its worktree and branch by itself (at startup, after each task ends, and every 10 minutes); its card then says merged · cleaned up. A worktree with uncommitted files, or a branch that is not merged, is left alone; files git ignores (such as .env) do not count as changes and are removed with it. A squash merge is not recognised, so use Discard for those.

The verifier

When a sub-agent ends its turn, Donezo starts a brand-new agent, the verifier, to check the Done means. No agent grades its own work.

Every pass or fail goes back to the director as a message. It does not need to keep asking.

The Team tab

The Team tab. A row of counts sits on top, with a filter and a Delegate a task button. Below are four columns of sub-agent cards, and on the right the decision log and the team rules.
The board on the left, the decision log and team rules on the right.

The row on top counts what is working and verifying now, plus what passed, failed, and was sent back to fix in the last 24 hours. The filter switches between Active and recent, All and Failed. With two or more directors, another filter appears (All directors). Scrolling loads more, 10 at a time.

ColumnMeaning
BuildingWaiting to start, working, or fixing after a failed check.
VerifyingA verifier is checking. The card shows the Done means.
PassedVerified. The card shows the commit and that the director was told.
FailedOut of attempts or stopped, with what the verifier found. Cancelled work is listed here too, under the All filter.

Buttons on a card depend on its stage:

The director's own panel on the canvas shows the same cards for its team. Its button Whole team & settings leads here.

The Board tab

Every agent you made (not its sub-agents) has a board: the backlog of work it holds. Pick the agent at the top; it opens on the one with the most proposals waiting, otherwise the most open cards. Cards sit in four columns: To do, In progress, Done and Dropped (folded until you click Show).

A card in a column shows only its number and title, so the columns stay easy to scan. The number, such as #12, is the one you and the agents use to name a card (card_id in the board tools). Click a card, or focus it and press Enter, to open it: the window shows who added it, the full details, the source link, the note and every action. Close, Escape or a click outside closes it. While it is open it follows changes an agent makes to the card.

The board only holds work; sub-agents still do it. Cards stay when their agent is unregistered.

Proposals

A proposal is an idea the planner found while researching, with a link to where it found it. It waits in a Proposed column, first on the board, until you decide. Only you decide: no agent can approve or start a proposal on its own, not even the agent whose board it is on. An agent cannot reword a waiting proposal or bring back one you rejected; you still can.

Planner

Above the columns, each agent has a Planner. Switched on, it runs a scout every few days: a fresh Claude session that searches the web for trending projects, techniques and industry practice that fit the agent's product, and files at most three proposals on that agent's board. Zero is a normal result.

The panel shows when the next run is due and how the last one went: when, its status, how many proposals it filed, the tokens it used, and why it failed if it did.

Decision log

Why the director chose this is a list, newest first, of the decisions the director and sub-agents recorded: what they chose, why, and sometimes Evidence you can expand. Decisions about one sub-agent show its task id. Read it when you want to know why the work was split a certain way, or why a failure was dropped.

Team rules

Reflect

Reflect turns past failures into a better playbook. Nothing is written until you approve it.

  1. Open Improve playbooks under Team rules.
  2. Choose what to improve: a director's own role SKILL, or a playbook for this repository.
  3. Press Reflect. A read-only agent reads failed runs and verifier findings, then proposes a change. If nothing has gone wrong for that playbook yet, the app says so and nothing runs.
  4. Read the reasoning and the diff, then press Approve and write or Reject.
The Team rules panel with Improve playbooks open. A pending proposal for the bugfix playbook shows its reasoning, a diff adding one line, and Approve and write and Reject buttons.
A proposal waiting for you. An approved playbook change is saved in that repository under .orch/playbooks/.