mnemosyne_todo_add
Add tasks to a named to-do list in the human's backlog, optionally grouped under steps, in execution order. Use it after a conversation settles what to do, so every agreed action becomes a visible, concrete task.
Instructions
Put tasks into the human's To-do backlog (the To-do widget on their canvas) — in order, optionally under named steps. Use it when a conversation has settled WHAT to do: "make tasks out of everything we said we would do". Name the list ("list") — call once without it to be told the lists that exist on a LIST_NOT_FOUND answer — or pass create_list: true to make a new one. Never assume a default list. The host routes the write through the widget's own store, so what you file is exactly what the human sees. Works with the app closed on a dev install (the headless daemon reads the file); an npm install has no daemon and needs the app running. To read the backlog back or change what is in it, see mnemosyne_todo_list, mnemosyne_todo_update and mnemosyne_todo_lists.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| list | No | Displayed name of the destination list (case-insensitive), e.g. "En cours", "WIP", or a list the human created. Omitted = the first original list. Unknown name + create_list false = refused with the names that exist. | |
| color | No | Hex colour (#rrggbb) for a list being created. Optional; the host picks the next swatch otherwise. | |
| tasks | Yes | The tasks, in execution order. Each item is a string, or {"text": string, "group": string} where group is the STEP the task belongs to (e.g. "Step 1 · Mockup"); tasks with the same group are shown under one header in the list. One concrete, actionable line each; 300 characters max. | |
| create_list | No | Create the list named in "list" when it does not exist. Default false: an agent must not invent lists in someone's backlog without saying so. |