Agent skill · Workflow & Productivity

ralphy

Autonomous AI coding orchestration using the Ralph Wiggum technique and Ralphy CLI. This skill should be used when running AI agents in continuous loops until tasks complete, orchestrating multi-task development with PRD/YAML files, configuring parallel agent execution, or implementing the Ralph Wiggum autonomous development methodology. Triggers on mentions of ralphy, ralph, autonomous loops, PRD-driven development, or multi-agent orchestration.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill ralphy --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/agent/ralphy/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Ralphy & Ralph Wiggum Technique Ralphy is an autonomous AI coding orchestrator that runs agents on tasks until done. Built on Geoffrey Huntley's Ralph Wiggum technique - a continuous loop methodology where AI agents iterate until completion. ## Quick Reference ```bash # Single task ralphy "add dark mode" # From PRD/YAML ralphy --prd PRD.md ralphy --yaml tasks.yaml # Parallel execution ralphy --parallel --max-parallel 5 # With branches and PRs ralphy --branch-per-task --create-pr ``` ## Core Concepts ### The Ralph Wiggum Technique The foundational principle: run an AI agent in a loop until the job is done. ```bash # Minimal form while :; do cat PROMPT.md | claude ; done ``` **Key insight**: Failures inform improvements. When Ralph fails, tune the prompts like a guitar - add specific guidance based on observed failure patterns. ### Three-Phase Architecture 1. **Requirements Definition**: Discuss project, identify Jobs to Be Done (JTBD), break into topics 2. **Planning Loop**: Gap analysis between specs and code, generate IMPLEMENTATION_PLAN.md 3. **Building Loop**: Implement tasks, validate with tests, commit on success ## Ralphy CLI Usage ### Task Sources **Markdown PRD** (checkbo

What's inside
Steps it walks through
  1. Quick Reference
  2. Core Concepts
  3. The Ralph Wiggum Technique
  4. Three-Phase Architecture
  5. Ralphy CLI Usage
  6. Task Sources
  7. Parallel Execution
  8. Branch Workflow
  9. Engine Selection
  10. Project Configuration
  11. CLI Flags Reference
  12. The Ralph Loop Pattern
  13. Security Considerations
  14. Best Practices
Ships with 1 file
  • metadata.json
Commands it runs
Single task
ralphy "add dark mode"
From PRD/YAML
ralphy --prd PRD.md
ralphy --yaml tasks.yaml
Parallel execution
ralphy --parallel --max-parallel 5
With branches and PRs
ralphy --branch-per-task --create-pr
Minimal form
More from claude-skill-registry
All skills →
About this skill
What does the ralphy skill do?

Autonomous AI coding orchestration using the Ralph Wiggum technique and Ralphy CLI. This skill should be used when running AI agents in continuous loops until tasks complete, orchestrating multi-task development with PRD/YAML files, configuring parallel agent execution, or implementing the Ralph Wiggum autonomous development methodology. Triggers on mentions of ralphy, ralph, autonomous loops, PRD-driven development, or multi-agent orchestration.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill ralphy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going