ralph

Iterate through PRD stories until all pass and a reviewer verifies completion.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill ralph-dropsyoon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/dropsyoon/oh-my-claudecode/tree/main/skills/ralph
Command: npx skills add https://github.com/dropsyoon/oh-my-claudecode --skill ralph-dropsyoon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralph prevents complex work from being marked “done” prematurely by continuing until every PRD user story is fully satisfied and verified, then performing a final reviewer sign-off (with an optional cleanup pass).

Core Features & Use Cases

  • PRD-driven persistence loop: executes story-by-story until all passes: true and reviewer verification are achieved.
  • Automatic PRD refinement and validation: generates or loads prd.json, then replaces generic acceptance criteria with task-specific, verifiable ones.
  • Structured progress and retry safety: tracks progress.txt, persists state across iterations, and reruns only what’s needed.
  • Tiered reviewer verification: uses selectable reviewers (architect, critic, or codex) to validate against the exact acceptance criteria.
  • Mandatory deslop cleanup + regression re-verification: runs ai-slop-cleaner on changed files and re-checks tests/build/lint before completing.

Quick Start

Tell your agent: "ralph, keep going until done and verify each PRD story until every requirement passes."

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I ensure complex code tasks pass all acceptance criteria before finishing?

PRD-driven persistence loops prevent premature completion by executing multi-iteration tasks until all acceptance criteria pass and a designated reviewer verifies the final state.

How do I generate task-specific acceptance criteria for a PRD?

To generate task-specific acceptance criteria, the system automatically creates or loads a prd.json file and replaces generic requirements with verifiable, task-specific conditions to guide the execution loop.

Does the verification loop work with multi-iteration engineering tasks needing retries?

Yes, the verification loop is designed for multi-iteration engineering tasks needing reliable convergence across retries, tracking progress via a structured file and persisting state to rerun only what is needed.

Can I use different reviewers to verify code against acceptance criteria?

Yes, you can use tiered reviewer verification by selecting an architect, critic, or codex reviewer to validate the implemented code against the exact acceptance criteria defined in the prd.json.

What is the best way to clean up AI-generated code and prevent regressions?

The best way to clean up AI-generated code is running an automated cleanup tool on changed files, followed by mandatory post-cleanup regression re-verification to ensure tests, builds, and lint checks still pass.