← ClaudeAtlas

mnemo-looplisted

Use when a session is about to dispatch, deliver, or report on mnemo's background children, or when a message arrives from another session - which verbs are the session's own and which are the maintainer's
xyrlan/mnemo · ★ 2 · AI & Automation · score 66
Install: claude install-skill xyrlan/mnemo
# mnemo's loop, from inside a session Every `mnemo` command prints for the maintainer at a terminal. A session that reads that output takes the maintainer's next step for its own. This says which verbs are whose. ## Yours - **Read rules before writing code.** `list_rules_by_topic(topic, query="<the task>")`, then `read_mnemo_rule(slug)`. The SessionStart header lists the topics that exist. - **`mnemo dispatch <issue>…`** — one detached child per issue, each in its own worktree. `--may` defaults to `pr`: each child publishes its own pull request. Pass `--may none` when the maintainer said the work should not become a branch; do not withhold on your own judgement either way. - **`mnemo deliver <id>…`** — push and open the PR for exactly the ids named, for a child that published nothing. The approval is the id and it comes from the maintainer, after they read the diff; typing the command is yours. Do not hand the command back to them. - **`mnemo deliver --stop-done`** — stop finished children still running. It publishes and approves nothing; a child writes its briefing only once stopped, and most stop themselves, so this sweeps the rest. - **Report the ids and stop.** Children are detached; a finish reaches you as the notice below, a block never does. ## The maintainer's - `mnemo sessions`, `claude agents`, the mnemo-desktop queue — their view of the children. Dispatch prints `queue:` and `attach:` for them, not for you. - Answering a blocked child,