ralph

Loops task execution with parallel agent delegation until architect-verified completion.

Updated Feb 1, 2024
One-click install
npx skills add https://github.com/ogiboy/portfolio-app --skill ralph-ogiboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/ogiboy/portfolio-app/tree/main/.codex/skills/ralph
Command: npx skills add https://github.com/ogiboy/portfolio-app --skill ralph-ogiboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Complex coding tasks often get declared done prematurely: partial implementations pass as complete, tests get skipped, and edge cases are forgotten. Ralph prevents this by looping on a task until it is genuinely complete, requiring fresh verification evidence and explicit architect sign-off before allowing completion. ## Core Features & Use Cases - Persistence Loop: Keeps iterating on a task across retries, tracking state via omx state commands and resuming from where the previous iteration stopped. - Parallel Delegation: Fires independent subagent tasks simultaneously with explicit agent_type and reasoning_effort levels (low, medium, xhigh) matched to task complexity. - Mandatory Verification: Requires fresh test/build/lint output plus an architect subagent review, a deslop cleanup pass on changed files, and post-cleanup regression re-verification before completion. - Use Case: A user says "ralph: migrate the auth module to OAuth2 and don't stop until all tests pass." Ralph plans the work, delegates implementation and test lanes in parallel, runs the suite, gets architect approval, cleans up AI slop, re-runs regression, and only then reports completion. ## Quick Start Ask the agent to ralph the task of refactoring the payment module and keep iterating until all tests pass and an architect review approves the changes.

Frequently Asked Questions about ralph

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an AI agent keep working until a coding task is fully done?

Invoke ralph with your task, for example "ralph: implement the caching layer." It loops through execution, verification, and architect review iterations, refusing to complete until tests, builds, and lint all pass with fresh output.

How does ralph verify task completion before stopping?

Ralph runs fresh test, build, and lint commands and reads their actual output, then dispatches an architect native subagent for sign-off. It also runs a deslop cleanup pass on changed files and re-verifies regression before completing.

When should I use ralph instead of autopilot or a one-shot executor?

Use ralph when a task must be completed with verification and may span multiple iterations. Use autopilot for full idea-to-code pipelines, plan for exploration before committing, and a direct executor agent for quick one-shot fixes.

Does ralph support PRD-based task breakdown?

Yes, passing the --prd flag triggers a quick deep-interview, then creates a PRD at .omx/plans/prd-{slug}.md and a progress ledger at .omx/state/{scope}/ralph-progress.json with prioritized user stories that drive the loop.

What are the limitations of the ralph persistence loop?

Ralph stops and reports when blocked by missing credentials, unclear requirements, or down external services, and flags issues recurring across 3+ iterations as fundamental problems. It is not suited for exploratory planning or quick single-step fixes.