Issues and boards

New issues sit in the pool until someone takes them. Taking is a claim, not a copy: the issue moves to that person, so two people never work on the same thing without knowing. An issue can be assigned without being dispatched yet. Assigning says who; dispatching says where and when.

Create an issue with a title, plus a description, criteria, repository and priority when they help. To file several at once, paste them into the composer in the front-matter format. See Several at once.

Backlog order is run order: move an issue up to have it run sooner. An issue blocked by another is not handed to an agent until its blocker is done.

Issues shows the same issues two ways: a board with Backlog, In progress, In review and Done, or a list grouped by stage. Each repository connected through the GitHub App gets its own list.

Each project has Notes: shared context for agents, organised like a file explorer. A note is filed in a folder or bound to a repository. A run reads the pinned notes and the notes bound to its issue's repository. See What a run reads.