Update to Odyssey365

{
  "description": "Brainstorm on an Odyssey project board as a mindmap — put a central topic in the middle, branch ideas out in several directions, and turn chosen branches into tasks. Use when the user wants to \"map out\", \"brainstorm on my board\", \"break this idea down\", \"make a mindmap of\", or explore options visually before planning.",
  "included_files": [],
  "name": "board-mindmap",
  "skill_md_contents": "---\nname: board-mindmap\ndescription: Brainstorm on an Odyssey project board as a mindmap — put a central topic in the middle, branch ideas out in several directions, and turn chosen branches into tasks. Use when the user wants to \"map out\", \"brainstorm on my board\", \"break this idea down\", \"make a mindmap of\", or explore options visually before planning.\n---\n\n# Brainstorm as a mindmap\n\nA mindmap on an Odyssey board is a **relationship**, not a special card: one `mindmap` component is\nthe center, and any component becomes a branch by naming its parent with `mindmapParentId`. The\nboard's layout engine spreads the branches, so you never compute coordinates.\n\n## Steps\n\n1. **Agree on the center.** Restate the topic in a few words. Pick the board (existing one via\n   `list_projects`, or `create_project` after the user agrees to a name).\n2. **Sketch the tree in chat first**: 3–6 first-level branches, 2–5 ideas under each, two levels\n   deep at most. Ask whether to adjust before writing anything to the board.\n3. **Create the center.** `add_project_component` with `type: \"mindmap\"` and `text` = the topic.\n4. **Create the branches.** For each first-level branch, `add_project_component` with `type: \"text\"`\n   (or `roundRect` for emphasis), `text` = the branch label, `mindmapParentId` = the center's id, and\n   `mindmapDirection` spread across `right`, `left`, `down`, `up` so the map stays balanced. Add the\n   second-level ideas the same way with the branch as parent and the same direction as their branch.\n5. **Lay it out.** Call `tidy_board` once when the map is complete. Skip this if the board already\n   had components the user arranged by hand — tell the user they can use the app's auto-arrange\n   instead.\n6. **Turn ideas into action (optional).** When the user picks branches to act on, make an `itemTile`\n   list for them with `mindmapParentId` = that branch, then add tasks with `create_todo`\n   (`projectUid` + `attachToComponentId` = the list's id). Tasks stay linked to the branch they came\n   from.\n7. **Report back**: the center, the branches created, and any tasks made from them.\n\n## Guardrails\n\n- Keep labels short (under about six words); long text belongs in a note, not a branch.\n- Reuse an existing mindmap if `get_project` shows one on the same topic under `structure.mindmaps`.\n- Removing branches uses `delete_project_component` and needs an explicit yes from the user.\n"
}