Update to XMemo

{
  "description": "Explore options using relevant XMemo goals, constraints, decisions, and failed approaches. Use for brainstorming grounded in saved personal or project context; keep proposals tentative and persist only authorized outcomes.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 397
    }
  ],
  "name": "xmemo-brainstorm",
  "skill_md_contents": "---\nname: xmemo-brainstorm\ndescription: Explore options using relevant XMemo goals, constraints, decisions, and failed approaches. Use for brainstorming grounded in saved personal or project context; keep proposals tentative and persist only authorized outcomes.\n---\n\n# Brainstorm with XMemo\n\nCreate new options without losing the context that already shapes the work.\nFollow **frame → recall → diverge → challenge → converge → preserve**.\n\n## 1. Frame the exploration\n\nState the problem, desired outcome, decision horizon, known constraints, and\nwhat must remain open. Ask only for missing information that would materially\nchange the option space.\n\n## 2. Recall decision-relevant context\n\nUse `recall_context` for bounded background, `search_memory` for a named\ndecision or failed approach, and `get_project_summary` for a known project.\nRetrieve goals, prior decisions, constraints, preferences, unresolved items,\nand lessons—not broad history.\n\nLabel recalled items as current, potentially stale, or conflicting. Current\nuser instruction and verified evidence outrank saved context.\n\n## 3. Diverge deliberately\n\nGenerate several genuinely different approaches. For each include:\n\n- core idea and intended value;\n- assumptions and dependencies;\n- major trade-offs and risks;\n- reversibility and cost of being wrong;\n- evidence or experiment that would reduce uncertainty.\n\nDo not quietly collapse to the first plausible answer or treat a previous\ndecision as immutable when the user explicitly reopens it.\n\n## 4. Challenge and compare\n\nStress-test the strongest options against saved constraints and current\nevidence. Identify contradictions, missing evidence, second-order effects, and\ncriteria that distinguish the options.\n\n## 5. Converge with the user\n\nReturn:\n\n1. **Problem frame**\n2. **Relevant remembered context**\n3. **Option set**\n4. **Comparison and risks**\n5. **Recommended direction**\n6. **Open questions or experiments**\n7. **Decision required from the user**\n\nKeep the recommendation provisional until the user approves it.\n\n## 6. Preserve only approved outcomes\n\nIf the user authorizes saving, route only the requested outcomes below.\nApproval of a direction alone does not authorize persistence. Preserve the\nactual decision status and do not manufacture an approval milestone:\n\n- durable direction or rationale → `remember`;\n- correction to an existing concept → `update_memory`;\n- concrete follow-up → `todo`;\n- unfinished exploration and unresolved choices → `update_state`;\n- material approval milestone → `record_event`.\n\nPreview writes when their scope remains unclear; do not reconfirm an authorized\nbatch. Never store the raw brainstorm, discarded alternatives as facts, or\nunverified claims as decisions. Return a\ncompact receipt of what was saved, updated, or intentionally left tentative.\n\nRead `../xmemo-memory-steward/references/review-playbooks.md`,\n`../xmemo-memory-steward/references/memory-policy.md`, and\n`../xmemo-memory-steward/references/tool-routing.md` when detailed policy or\nrouting is needed.\n\n## Shared boundaries\n\nBefore any tool call, read and apply\n[plugin boundaries](../xmemo-memory-steward/references/plugin-boundaries.md).\nUse [tool routing](../xmemo-memory-steward/references/tool-routing.md) for unfamiliar\noperations, [temporal queries](../xmemo-memory-steward/references/temporal-queries.md)\nfor dates or chronology, and [memory policy](../xmemo-memory-steward/references/memory-policy.md)\nbefore writes. Reuse existing authorization; clarify only unresolved scope.\nReport failed or unconfirmed operations without claiming success.\n"
}