菜单
Review a proposed plan against XMemo's saved goals, decisions, constraints, lessons, project state, and acceptance criteria. Use for architecture plans, implementation plans, launch plans, or plans produced by Claude or another agent. Return a formal verdict and review gate; do not mistake a proposal for approved work or implemented progress.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Audit implementation or project progress against the approved XMemo plan, checkpoint, decisions, and current evidence. Use when Claude must verify another agent's completion report, reconcile multi-agent claims, identify drift or blockers, and determine the exact next action. Never promote a claim to verified state without evidence.
Run a structured XMemo-grounded brainstorm that recalls prior goals, constraints, decisions, and failed approaches; generates distinct options; tests them; and converges on a user-approved direction. Use when exploring ideas, product directions, architectures, strategies, or plans with Claude. Keep proposals tentative until the user approves them, and save only durable outcomes.
Turn an important Claude conversation or work session into concise, retrieval-ready XMemo outcomes. Use when summarizing key points, preserving decisions and rationale, extracting TODOs and unresolved questions, or saving unfinished progress. Do not archive raw transcripts, filler, secrets, or tentative ideas as confirmed facts.
Prepare or receive a professional XMemo handoff between Claude sessions or compatible AI agents such as Claude, Codex, GitHub Copilot, or Kiro. Use when switching agents, transferring unfinished work, reconciling a received handoff, or preserving a restart-ready package with provenance, evidence, blockers, and one exact next action.
Use XMemo to recall and preserve durable project context, decisions, plans, TODOs, checkpoints, and cross-agent handoffs. Use when resuming work, distilling an important conversation, reviewing a brainstorm or implementation plan against saved context, recording progress or blockers, handing work between Claude and another compatible agent, or managing memory lifecycle actions. Never save raw transcripts, secrets, or tentative ideas as confirmed decisions.
Design or revise an evidence-gated project plan and executable Markdown plan using XMemo context and the live workspace. Use when starting a project, turning goals or a brainstorm into PROJECT_PLAN.md and EXECUTION_PLAN.md, decomposing work into phases and acceptance gates, assigning multi-agent ownership, or correcting a plan after review. Keep proposals distinct from approved decisions and implemented progress.
| name | review-plan |
| description | Review a proposed plan against XMemo's saved goals, decisions, constraints, lessons, project state, and acceptance criteria. Use for architecture plans, implementation plans, launch plans, or plans produced by Claude or another agent. Return a formal verdict and review gate; do not mistake a proposal for approved work or implemented progress. |
Test a proposal against durable context before work begins. Follow scope → baseline → decompose → challenge → verdict → gate.
Identify the plan version, intended outcome, project or scope, decision owner, risk tolerance, and required review depth. Distinguish a draft, proposed plan, approved plan, and implemented state.
Use recall_context for the bounded decision set, search_memory for exact constraints or prior choices, get_project_context for project state, and todo for active commitments. Retrieve only what can materially affect the review.
Resolve conflicts by current user instruction, verified evidence, recency, and scope. Memory is context, not automatic authority.
Map goals, assumptions, dependencies, sequence, ownership, rollback, verification, acceptance criteria, and unresolved decisions. Identify steps that are too broad to verify or that silently expand scope.
Check:
Use explain_memory when the provenance or match rationale of a decisive memory is unclear.
Use this structure:
approved, changes_requested, blocked, or rejectedMake findings specific enough to act on. Separate blocking issues from optional improvements.
Do not save the proposal as approved unless the user approves it. After approval:
remember or update_memory;create_pending_decision;todo;update_state.Preview multi-record writes and return a receipt. Never claim implementation or deployment merely because the plan passed review.
Read ../memory-steward/references/review-playbooks.md, ../memory-steward/references/memory-policy.md, and ../memory-steward/references/tool-routing.md for detailed gates and routing.