Concepts
Tasks
The implementation queue that connects work to the specifications an agent needs for it.
What is a Task?
A Task is one unit of implementation work in a project's queue. It has a title, an optional description, and can link to one or more Specifications the agent needs to do the work correctly.
Lifecycle
A Task moves forward through four states, in order:
| Status | Meaning |
|---|---|
ready | Queued, not started. |
analysing | An agent has picked it up and is working out what to do. |
implementing | Actively being implemented. |
implemented | Done. This is the final state. |
When an agent drives these transitions through MCP tools, they only move forward one step at a time — ready → analysing → implementing → implemented. You can also set a Task's status directly from the dashboard.
Relation to Specifications and Rulesets
A Task links to the Specifications relevant to it — not to Rulesets. Rulesets already reach the agent on every prompt regardless of which Task is active, so a Task only needs to point at the system knowledge specific to that piece of work.
How an agent works with a Task
Through MCP tools, an agent can:
- Ask for the next Task in the ready queue (
xorox_get_next_task), or list Tasks by status (xorox_list_tasks). - Start one, moving it to
analysingand claiming it if unassigned (xorox_start_task). - Move it to
implementing(xorox_set_task_status). - Mark it
implementedwhen done (xorox_mark_task_implemented).
See MCP tools for exact arguments and return values.