MonoClaw

Kanban Multi-Agent

The Kanban board is a durable task management system built into MonoClaw. It lets you coordinate work across multiple Mona profiles using a SQLite-backed board.

Creating a board

monoclaw kanban create "Project Alpha"

Adding tasks

monoclaw kanban add "Project Alpha" \
  --title "Refactor auth module" \
  --description "Move auth logic into a dedicated service" \
  --assignee work \
  --label refactoring

Board columns

Default columns:

  • Backlog — Ideas and future work
  • Todo — Ready to start
  • In Progress — Currently working
  • Review — Ready for review
  • Done — Completed

Custom columns

monoclaw kanban columns "Project Alpha" --set "Backlog,Todo,In Progress,Review,Done,Archived"

Moving tasks

monoclaw kanban move "Project Alpha" 3 --to "In Progress"
monoclaw kanban move "Project Alpha" 3 --to "Done"

Viewing the board

monoclaw kanban show "Project Alpha"

Output:

Project Alpha
=============

Backlog
  #5  Update documentation

Todo
  #4  Fix login bug

In Progress
  #3  Refactor auth module  [@work]

Review
  #2  Add password reset

Done
  #1  Set up CI/CD

Multi-agent coordination

Different Mona profiles can claim and work on tasks:

# Profile: work
monoclaw kanban claim "Project Alpha" 3
monoclaw kanban move "Project Alpha" 3 --to "In Progress"

# Later, when done
monoclaw kanban move "Project Alpha" 3 --to "Review"

# Profile: review
monoclaw kanban claim "Project Alpha" 3
monoclaw kanban move "Project Alpha" 3 --to "Done"

Task automation

Link cron jobs to kanban tasks:

monoclaw cron create "0 9 * * *" \
  "Check the Project Alpha kanban board. Summarize what's in progress and what's blocked." \
  --deliver slack

Board storage

Boards are stored in ~/.monoclaw/kanban.db (SQLite). They are:

  • Portable — copy the database to share boards
  • Durable — survive restarts and crashes
  • Queryable — use SQL for advanced reporting

Best practices

  • One board per project — Keep tasks focused
  • Use labels — Tag tasks by type (bug, feature, refactoring)
  • Assign profiles — Clarify who does what
  • Archive old tasks — Keep the board clean
  • Link to sessions — Reference session IDs in task descriptions for context