Menu
Use as an explicit compatibility alias for execute when the user wants completion-gated implementation that keeps going until proof is gathered.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | ralph |
| description | Use as an explicit compatibility alias for execute when the user wants completion-gated implementation that keeps going until proof is gathered. |
| argument-hint | [task, implementation handoff, or completion-gated execution request] |
Treat this as a compatibility alias of execute, not as a separate canonical workflow stage.
execute workflow semanticsagmo-executor handles coding and agmo-verifier provides the completion gate verdictteam only when implementation and verification truly need durable parallel lanesWhen 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.
ralph means:
Before ending a meaningful completion-gated stage, make the final response or delegated result save-ready:
team when durable worker lanes are genuinely neededUse execute in docs, onboarding, and workflow descriptions. Keep ralph available so users can explicitly ask for a completion-gated execution pass without introducing a separate workflow stage.