菜单
Use when a plan should be challenged, approved, or refined before implementation starts, with agmo-critic/agmo-architect/verifier routing as needed.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use as the canonical first-stage Agmo workflow when the user wants idea exploration, design tradeoffs, or requirement shaping before planning or implementation.
Run a Codex-native structured code review using agmo-critic and agmo-verifier where evidence is needed.
Harvest `debt:` markers across the repo into a read-only ledger without modifying code.
Audit and maintain the vault-backed llm-wiki knowledge base, including stale pages, low-confidence or contested captures, superseded captures, missing frontmatter, and broken wikilinks.
Use when prior notes, durable project knowledge, or vault-backed context should influence the current task.
Use when one execution lane is no longer enough and work should escalate to the durable `agmo team ...` runtime.
| name | plan-review |
| description | Use when a plan should be challenged, approved, or refined before implementation starts, with agmo-critic/agmo-architect/verifier routing as needed. |
| argument-hint | [current plan, plan note, or review request] |
Use this when the current plan should be challenged, validated, or refined before execution.
The main session must not self-approve its own plan.
When $plan-review is invoked, the main session should:
agmo-explore before judging plan assumptions tied to current files or symbolsagmo-criticagmo-architectagmo-verifieragmo-plannerWhen spawning native subagents for this workflow, keep each agent id until its result is integrated, then call close_agent for completed, failed, superseded, or no-longer-needed lanes so thread slots are released before the next delegation.
Check the plan for:
executeplanbrainstormingBefore ending a meaningful plan-review stage, make the final response or delegated result save-ready: