Build, review, document.

Open Folder Settings → Auto-code, turn Auto-code on, and choose Code + review + docs · Mo-driven. The graph has three cli_agent nodes: an implementer, a reviewer with Claude as fallback, whose review can send the diff back to the implementer, and a docs agent that runs only after the review passes.

Mo sits between every pair of stages. After the implementer, Mo can stop the run and ask you in chat, through a human_gate, when the diff raises a question only you can answer. After the reviewer approves, the docs agent starts, and Mo checks the docs against the diff before the ticket closes.

There is a four-agent variant, "Code + review + docs + QA", where a QA agent adds functional tests or a manual checklist after the docs.

The docs node’s prompt is yours to edit. Name the files that must stay in sync: README, the docs folder, the changelog. Then state the rule: describe what shipped, in the diff, not what the ticket asked for.

The agent sees the ticket, the implementer’s summary, the review and the list of changed files. So it documents the real change, not the plan.

The docs agent works in the repository only: it edits files such as the README, the docs and the changelog, and it cannot write Morion notes. If you keep a release log in Morion, write that note after the run, yourself or through your agent over MCP.

Move a ticket to Todo. The implementer builds. The reviewer writes a review, and Mo decides. The docs agent updates three files. The ticket lands in Done with the diff and the docs on its own branch; you merge it with one click in the Auto-code drawer, or let the folder auto-merge.

When the review asks for changes, Mo sends the diff back to the implementer in the same run, with the review in context. The docs step waits until a review passes, so it never documents a rejected diff.

When the implementer comes back with a question, Mo stops the run at the human_gate and asks you in chat. Answer there.

The run resumes with your reply in context, and the implementer gets your words in its packet. The docs step still waits for a passing review.

Docs that describe the code as it is, written by an agent that read the diff and the review, after the reviewer approved the diff. If you keep a release log in Morion, have your agent write the entry after the run; Ask Mo can then answer questions about it with citations.