ralph

Iterate through PRD-defined user stories until reviewer-verified against acceptance criteria.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Moliboy5000/.claude --skill ralph-moliboy5000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/Moliboy5000/.claude/tree/main/plugins/cache/omc/oh-my-claudecode/4.8.2/skills/ralph
Command: npx skills add https://github.com/Moliboy5000/.claude --skill ralph-moliboy5000

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures complex tasks are fully completed and verified, preventing silent failures and partial implementations.

Core Features & Use Cases

  • Persistence Loop: Iteratively works on a task until all user stories are passed and verified.
  • PRD-Driven Execution: Structures work into discrete, verifiable user stories defined in prd.json.
  • Mandatory Verification: Requires reviewer sign-off against specific acceptance criteria before completion.
  • Use Case: For a feature requiring multiple development steps and thorough testing, Ralph ensures each step is completed and signed off before declaring the entire feature done.

Quick Start

Use the ralph skill to complete the task described in the prompt, ensuring all user stories in prd.json are passed and verified.

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I ensure task completion and prevent silent failures during complex software development?

Task completion with verification is ensured by orchestrating a persistent, PRD-driven development loop that iterates through user stories until all are completed and reviewer-verified against acceptance criteria. This prevents partial implementations and silent failures.

How do I structure work into discrete user stories for iterative development?

Structuring work into discrete, verifiable user stories is done using a prd.json file for story definition. The system uses this file to drive execution, tracking progress iteratively until every story passes mandatory verification.

What's the best way to automate retries and track progress for multi-step feature development?

Automating retries and tracking progress for multi-step development requires a persistence loop that manages task persistence and logs iterations in a progress.txt file. It automatically retries tasks until all user stories receive reviewer sign-off.

Do I need a specific file format to define acceptance criteria for development tasks?

Yes, you need a prd.json file to define user stories and their specific acceptance criteria. The system requires this file to structure the work and mandate reviewer verification before declaring the entire feature done.

Can I use PRD-driven execution for features requiring thorough testing and mandatory reviewer sign-off?

PRD-driven execution is ideal for features requiring thorough testing and mandatory reviewer sign-off. It ensures each development step is completed and signed off against acceptance criteria before the entire feature is declared done.