Agent skill · Documentation

ralph-wiggum

Ralph Wiggum iterative development loop methodology for persistent AI agent work. Implements continuous iteration loops where AI works on tasks until completion, using Archon for state management and context handoffs. Integrates with The Long Run Harness, Spec Kit, and PRP frameworks. Triggers: ralph, wiggum, iteration loop, persistent agent, continuous development.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill ralph-wiggum-fgarofalo56-suppercharge-microso --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Version: 1.0.0
Path: skills/agent/ralph-wiggum-fgarofalo56-suppercharge-microso/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

# Ralph Wiggum - Iterative AI Development Loops > **"Ralph is a Bash loop"** - A simple `while true` that repeatedly feeds an AI agent a prompt, allowing it to iteratively improve its work until completion. ## 🚀 Quick Start | Command | Description | |---------|-------------| | `/ralph-start` | Launch the setup wizard | | `/ralph-iterate` | Run one iteration manually | | `/ralph-status` | Check loop status & progress | | `/ralph-cancel` | Cancel active Ralph loop | | `/ralph-integrate` | Integrate Ralph with other frameworks | --- ## What is Ralph Wiggum? Ralph Wiggum is a development methodology based on continuous AI agent loops. Named after Ralph Wiggum from The Simpsons, it embodies the philosophy of **persistent iteration despite setbacks**. ### Core Concept ``` ┌─────────────────────────────────────────────────────────────────────┐ │ RALPH WIGGUM LOOP │ │ │ │ ┌──────────┐ │ │ │ PROMPT │ ◄────────────────────────────────────┐ │ │ └────┬─────┘ │ │ │ │ │ │ │ ▼ │ │ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ │ │ │ AGENT │───►│ WORK │───►│ CHECK │─────┤ │ │ │ START │ │ ON TASK │ │ COMPLETE │ │ │ │ └──────────┘ └──────────┘ └────┬─────┘ │ │ │ │ │ │ │ ┌──────────┴───────┐ │ │ │ │ │ │

What's inside
Steps it walks through
  1. 🚀 Quick Start
  2. What is Ralph Wiggum?
  3. Core Concept
  4. Self-Referential Feedback Loop
  5. Philosophy
  6. 1. Iteration > Perfection
  7. 2. Failures Are Data
  8. 3. Operator Skill Matters
  9. 4. Persistence Wins
  10. Execution Modes
  11. Mode 1: Background Workflow
  12. Mode 2: Manual Iteration
  13. Mode 3: Hybrid (Recommended)
  14. Loop Termination
Ships with 1 file
  • metadata.json
Commands it runs
Start Ralph in background (recommended for long-running tasks)
Run one iteration
Check status
Continue if needed
First few iterations - supervised
Once confident, go to background
Use Ralph for harness coding sessions
Ralph wraps harness-coder with iteration loop
Use Ralph for spec implementation
Ralph iterates until spec requirements met
More from claude-skill-registry
All skills →
About this skill
What does the ralph-wiggum skill do?

Ralph Wiggum iterative development loop methodology for persistent AI agent work. Implements continuous iteration loops where AI works on tasks until completion, using Archon for state management and context handoffs. Integrates with The Long Run Harness, Spec Kit, and PRP frameworks. Triggers: ralph, wiggum, iteration loop, persistent agent, continuous development.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill ralph-wiggum-fgarofalo56-suppercharge-microso --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