Update to XMemo

{
  "description": "Create or revise project and execution plans using XMemo context and available artifacts. Use to turn goals into scoped phases, dependencies, and acceptance gates; distinguish proposed work from approved or completed work.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 416
    },
    {
      "relative_path": "assets/execution-plan-template.md",
      "size_in_bytes": 1691
    },
    {
      "relative_path": "assets/project-plan-template.md",
      "size_in_bytes": 1292
    },
    {
      "relative_path": "references/plan-quality-gates.md",
      "size_in_bytes": 2159
    }
  ],
  "name": "xmemo-plan-project",
  "skill_md_contents": "---\nname: xmemo-plan-project\ndescription: Create or revise project and execution plans using XMemo context and available artifacts. Use to turn goals into scoped phases, dependencies, and acceptance gates; distinguish proposed work from approved or completed work.\n---\n\n# Plan a Project with XMemo\n\nTurn intent into reviewable, executable artifacts. Follow\n**discover → recall → frame → decompose → gate → write → approve → checkpoint**.\n\n## 1. Discover the planning surface\n\nInspect the live project or supplied artifacts before designing the plan.\nIdentify canonical documentation, existing plans, architecture, test and\nrelease commands, ownership conventions, and dirty-worktree boundaries. If the\nactive surface cannot inspect them, label the baseline unverified instead of\ninventing commands, paths, or completed work.\n\nClarify whether the request needs a strategic project plan, implementation or\nmigration plan, release plan, recovery plan, or both stable and executable\nplans.\n\n## 2. Recall relevant context\n\nUse `recall_context` or `get_project_summary` for goals, constraints, decisions,\nrejected approaches, risks, acceptance criteria, and latest verified state.\nUse `search_memory` for exact decisions or lessons. Reconcile memory with live\nevidence; do not use memory as proof.\n\n## 3. Frame the project contract\n\nDefine:\n\n- problem, users, and desired outcome;\n- in-scope and explicitly out-of-scope work;\n- current verified baseline;\n- constraints and invariants;\n- success measures and acceptance evidence;\n- assumptions, dependencies, and unresolved choices.\n\nKeep unresolved choices visible in the draft. If checkpoint saving is authorized,\npreserve blocking choices in `update_state`; do not silently turn them into decisions.\n\n## 4. Decompose executable work\n\nFor each independently reviewable phase include objective, rationale, exact\nscope, artifacts, dependencies, owner, ordered steps, verification evidence,\nacceptance gate, recovery path, and handoff condition. Keep implementation,\nreview, merge, deployment, and production verification as distinct states.\n\n## 5. Design evidence gates\n\nMap every requirement to tests, inspection, review, deployment evidence, or\nuser acceptance. Add security, privacy, compatibility, data-loss, migration,\nand operational controls when applicable. Read\n`references/plan-quality-gates.md` before producing a formal plan.\n\n## 6. Write Markdown artifacts\n\nRespect repository conventions. When none exist and the user requests files,\nuse:\n\n- `PROJECT_PLAN.md` for stable purpose, scope, architecture, milestones, risks,\n  and success criteria;\n- `EXECUTION_PLAN.md` for ordered phases, status, evidence gates, ownership, and\n  the exact next action.\n\nAdapt `assets/project-plan-template.md` and\n`assets/execution-plan-template.md`; do not copy irrelevant sections.\n\n## 7. Review and approve\n\nReturn files changed, unresolved choices, assumptions, critical risks, first\nacceptance gate, and exact next action. Label approval status accurately and\nreuse approval already given in this task.\nUse `$xmemo-review-plan` for a formal review.\n\n## 8. Preserve the approved state\n\nWhen saving is authorized, preserve only the requested record types. Plan\napproval alone does not authorize these writes:\n\n- save durable decisions and constraints with `remember` or `update_memory`;\n- create only concrete near-term actions with `todo`;\n- save the active phase, verified baseline, blocker, and next action with\n  `update_state`;\n- record material approval or a phase transition with `record_event`;\n- create a formal XMemo project with `project` only when explicitly requested.\n\nDo not mirror the entire plan into XMemo or mark planned work as implemented.\nRead `../xmemo-memory-steward/references/memory-policy.md`,\n`../xmemo-memory-steward/references/workflows.md`, and\n`../xmemo-memory-steward/references/tool-routing.md` for write, checkpoint, and\nrouting rules.\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"
}