Projects & board

Mnema has a Kanban board and projects for organising work. These are generalist — every workspace has them, not just dev-mode ones. A board can carry engineering tasks, meeting action items, and business to-dos side by side.

The board

Tasks move through a fixed set of states:

backlog → in_progress → review → done
                  ↓
              audit_fix   (a blocker was logged; needs a fix)

Each task has a priority, optional assignee, free-form tags, and can link to a doc or a meeting. Agents drive the same board through MCP tools — get_next_task, claim_task, complete_task, log_blocker — so human and agent work share one board.

Projects

A project groups tasks, docs and meetings under one name, colour and status. Assign a task to a project to roll its work up; connect a project to a GitHub repo to attribute merged PRs back to the tasks that produced them.

Sprints

Group a set of tasks into a sprint with the create_sprints MCP tool. Sprints are lightweight — they tag tasks rather than living in a separate table — so an agent can plan a sprint in one call and you can filter the board by it.

Blockers and retries

When an agent hits a wall it calls log_blocker, which moves the task to audit_fix, records the reason, and schedules an automatic fix-retry with an AI-generated hint. A workspace member can also review it. The next agent that claims the task sees the hint via get_next_task.