Use cases

Running an epic.

A task too big for one session needs a board. Write the epic as one note, let your agent split it into tickets, let agents claim them one at a time, and the board keeps the record of each one. Twenty minutes to set up; then it runs as long as the epic does.

20 minany MCP agent · Mocolumns: note · backlog · todo · doing · review · reopened · done

1Write the epic and split it

Write the epic as one note in the project’s kanban folder and keep it in the Note column, where no agent can claim it. It holds the goal, the constraints, and what done looks like for the whole thing. It never moves. Every ticket points back to it.

Then ask your agent to split it. You get a list of tickets, each with a title, acceptance criteria and its dependencies, named in plain words. Mo relates the tickets to the epic through topics and through the words they share. You do not wire links by hand.

you Read the epic "Offline mode" in Morion. Split it into tickets of half a day each. For each: title, acceptance criteria, which other tickets it depends on. Create them in the same folder, all in Backlog. Move the ones with no dependencies to Todo. claude notes_get "Offline mode" notes_create "Queue writes while offline" · todo notes_create "Replay the queue on reconnect" · backlog · depends: queue notes_create "Conflict marker on divergent edits" · backlog · depends: replay notes_create "Offline banner and retry control" · todo notes_add_comment on "Offline mode": "Split into 4 tickets: …"

2Let agents claim tickets

you → Claude CodeTake the next task on Offline mode.

The agent lists the Todo column, picks the top ticket and calls mo_take_task with claim: true. The ticket moves to Doing in the same call that returns its work packet. If a second agent reaches for the same card, its claim comes back claimed: false and it takes the next one.

Progress goes on the ticket as comments, not in the chat. “Schema done, replay pending” on the card is worth more than the same sentence in a transcript. The next session, the reviewer and Ask Mo can all read it.

Queue writes while offline · activitydoing
mcp:claude-code
tasks_claim · todo → doing
mcp:claude-code
notes_add_comment · "Outbox table added; writes enqueue when the socket is closed. Replay is the next ticket."
mcp:claude-code
mo_request_human · "Should queued deletes also queue, or apply immediately? Not decided in the notes."
user
notes_add_comment · "Queue them. Deletes replay in order like everything else."
mcp:claude-code
tasks_move · doing → review · "Tests green, 11 cases"

3Answer questions on the ticket

An agent that hits a decision it cannot make calls mo_request_human. That is a durable comment on the ticket or a card in the backlog, not a chat that blocks. Your agent cannot ping you, so it will also tell you in its own chat to check Morion. You answer when you see it, in the app or from any agent. The answer becomes part of the ticket’s story, and the next run reads it.

you → the ticket, as a commentQueue them. Deletes replay in order like everything else.

4Review, re-open, close

Done is your column. Agents stop at Review. When a reviewed ticket is not right, do not delete it and do not write a new one. Move it to Re-opened and say what is wrong in a comment. The card records who sent it back; in the card drawer, pick what happens next: New session, Ask human, or Resume session. Both travel with the card, so whoever picks it up next starts from the failure instead of from zero.

Move to Done yourself. Done is the one column only you move.

Offline mode · Kanban
Note
Offline mode
epic · 4 tickets
Todo
Replay the queue
unblocked today
Re-opened
Offline banner
!Retry fires twice on reconnect. Resolution: Resume session.
Done
Queue writes
11 tests green

5Ask Mo what is left

Ask Mo, scoped to the project and to the open statuses. The answer lists what is in each column, with a citation per claim. It also lists the gaps: things the epic mentions that no ticket covers. That is the planning meeting, and it takes a minute.

you What is left on Offline mode, and is there anything in the epic that no ticket covers? claude mo_ask {projectId: …, statuses: ["backlog","todo","doing","review","reopened"], question: "…"} Open: Replay the queue (todo), Offline banner (re-opened, retry fires twice), Conflict marker (backlog). Done: Queue writes. Gap: the epic says "sync attachments too"; no ticket covers attachments.

6Questions

Can two agents take the same ticket?

No. The claim is atomic: one agent gets the card and moves it to Doing, the other gets claimed: false and takes the next one.

What happens when an agent needs a decision?

It posts the question on the ticket, marked as awaiting a human. You answer in a comment, in the app or from any agent, and the next run reads it.

7What you have now

An epic that outlives any one session. The plan sits on the board, each ticket carries its own progress, questions and reasons, and any agent you point at the folder picks up the next unclaimed piece with the related notes and tickets in its packet. You move cards to Done and ask Mo for the state of play. Nothing depends on a transcript you have to find again.

Download