ralph

Automate multi-iteration task delivery with PRD-driven persistence and reviewer verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the disciplined, multi-iteration execution of complex tasks by enforcing a PRD-driven loop and mandatory reviewer verification, ensuring every user story is fully implemented and validated before completion.

Core Features & Use Cases

  • PRD-driven iteration: break tasks into verifiable stories and track progress across iterations.
  • Automatic persistence and retries: continue work after failures and persist state between attempts.
  • Reviewer verification: require fresh validation against acceptance criteria before marking completion.

Quick Start

Start Ralph with a task description and let it iterate until all acceptance criteria are met and reviewer verification passes.

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I automate multi-iteration task delivery with reviewer verification?

Automated multi-iteration task delivery uses a PRD-driven persistence loop to break tasks into verifiable user stories, applying automatic retries until all acceptance criteria pass formal reviewer sign-off.

What is PRD-driven iteration for long-running project automation?

PRD-driven iteration is an automated workflow that breaks complex development tasks into traceable user stories, tracking progress across multiple persistent retries until every story satisfies formal acceptance criteria.

How do I enforce acceptance criteria and reviewer sign-off for automated workflows?

To enforce acceptance criteria and reviewer sign-off, configure an automated persistence loop that requires fresh validation against PRD requirements before marking any user story as fully complete.

Can I use PRD-based story tracking for complex tasks that require persistent state?

Yes, PRD-based story tracking supports long-running complex tasks by persisting state between automated retries, ensuring traceable progress and mandatory post-review verification across all iterations.

What's the best way to handle automated retries for failed user stories in a development workflow?

The best way to handle automated retries for failed user stories is using a PRD-driven persistence loop that automatically continues work after failures and validates against reviewer criteria before completion.

Why does my automated task workflow lack traceable progress across multiple iterations?

Automated task workflows lack traceable progress when they fail to persist state between retries or omit a PRD-driven loop that enforces reviewer verification for each user story before final completion.