Menu
Use as an explicit compatibility alias for consensus-oriented planning when the user wants a higher-trust plan before execution.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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 | ralplan |
| description | Use as an explicit compatibility alias for consensus-oriented planning when the user wants a higher-trust plan before execution. |
| argument-hint | [task, approved design, or consensus planning request] |
Treat this as a compatibility alias of plan, not as a separate canonical workflow stage.
plan workflow semanticsagmo-explore for repo facts before debating internals the codebase can answeragmo-architect for boundary and tradeoff reviewagmo-critic when the plan needs a stronger challenge pass before executionplan-review or executeWhen 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.
A strong ralplan result should usually include:
Before ending a meaningful consensus-planning stage, make the final response or delegated result save-ready:
ralplan should not auto-start implementation. It is still a planning-lane workflow.
Use plan in docs, onboarding, and workflow descriptions. Keep ralplan available so users can explicitly ask for a consensus-style planning pass without introducing a separate workflow stage.