ralph

Orchestrate state-managed execution loops with planning, review, and verification gates.

10|Updated May 9, 2026
One-click install
npx skills add https://github.com/jcwleo/oh-no-harness --skill ralph-jcwleo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/jcwleo/oh-no-harness/tree/main/plugins/oh-no-harness/skills-claude/ralph
Command: npx skills add https://github.com/jcwleo/oh-no-harness --skill ralph-jcwleo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of vague, unverified, or poorly planned coding tasks by enforcing a rigorous, state-managed execution loop that ensures every change is planned, reviewed, and verified against acceptance criteria.

Core Features & Use Cases

  • Mode-Gated Execution: Automatically selects between LIGHT, STANDARD, and THOROUGH execution modes based on risk and complexity.
  • Verification-First Workflow: Enforces test-driven development and independent verification to ensure code quality and behavior correctness.
  • Use Case: Use this when you have a concrete feature request or bug fix and need to ensure the implementation is fully tested, reviewed, and integrated without manual oversight or risk of scope creep.

Quick Start

Invoke the ralph skill by providing the path to your approved plan or concrete task specification to begin the execution loop.

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I automate complex coding tasks with strict test-driven verification?

Automate complex coding tasks by passing an approved plan to a state-managed execution loop that enforces planning, review, and TDD-based verification gates for high-confidence behavior changes.

What is the best way to enforce independent verification during code refactoring?

Enforce independent verification during refactoring by using a mode-gated execution loop that generates TDD-based evidence and checks acceptance criteria before any behavior-changing edits are integrated.

How do I prevent scope creep when executing a concrete bug fix?

Prevent scope creep during bug fix execution by isolating changes in a worktree and passing a concrete task specification through strict review and verification gates.

Does this automated workflow execution support different complexity levels?

Automated workflow execution supports different complexity levels by automatically selecting between LIGHT, STANDARD, and THOROUGH execution modes based on the specific task's risk and complexity.

When do I need a state-managed execution loop for software development?

You need a state-managed execution loop for software development when implementation, refactoring, or debugging scenarios require high confidence, auditability, and verified behavior-changing edits.

Why does my automated coding workflow require an approved plan?

Automated coding workflows require an approved plan to establish the concrete task specification needed to begin the state-managed execution loop and enforce rigorous planning and verification gates.