---

name: runner-ralph description: Instructions for configuring and running the Runner Ralph autonomous development loop. Use when the user wants to start an automated coding session, configure a PRD, or understand how to use the runner script.

Runner Ralph

This skill provides instructions on how to use scripts/runner-ralph/ralph.py, an autonomous agent runner that implements a PRD-driven development loop.

Purpose

Runner Ralph runs AI coding agents (Claude Code or Cursor) in a loop to complete user stories defined in a prd.json file. It handles:

• Git branching and merging per story
• Progress tracking and work logging
• Iterative execution until acceptance criteria are met

1. Prerequisites

Ensure the environment is set up:

1. Install uv: curl -LsSf https://astral.sh/uv/install.sh | sh
2. Install an Agent CLI:
   • Cursor: curl https://cursor.com/install -fsS | bash (Preferred)
   • Claude: npm install -g @anthropic-ai/claude-code

2. Configuration: prd.json

The runner is driven by a prd.json file in the project root.

File Format:

Copy{
  "projectName": "My Project",
  "branchName": "feature/my-feature",
  "userStories": [
    {
      "id": "story-1",
      "title": "Implement user authentication",
      "description": "Add login and registration functionality",
      "type": "feature",
      "spec": [
        "Support password reset via email",
        "Use existing user table"
      ],
      "acceptanceCriteria": [
        "Users can register with email/password",
        "Users can log in",
        "Failed logins show error messages"
      ],
      "passes": false
    },
    {
      "id": "story-2",
      "title": "Complex Dashboard",
      "description": "Add a complex analytics dashboard",
      "type": "feature",
      "specFile": "specs/dashboard-spec.md",
      "acceptanceCriteria": [
        "Dashboard loads within 2 seconds",
        "All charts display correct data"
      ],
      "passes": false
    }
  ]
}

Fields:

• type: Optional. Can be feature, bug, chore, test. Triggers specialized prompts (e.g., prompt_feature.md).
• spec: Optional. Inline list of additional requirements or implementation notes.
• specFile: Optional. Path to an external markdown file containing the full feature specification. This is preferred for complex features.
• passes: Set to true by the runner when complete.

3. External Feature Specs

For complex features, it is recommended to use the specFile field instead of inline spec strings. This allows you to provide much more detail, including user flows, UX considerations, and technical constraints, without cluttering the prd.json.

Using specFile vs Inline spec

• Inline spec: Best for small tasks or simple bug fixes.

  Copy"spec": ["Fix CSS padding on mobile", "Update logo to new SVG"]
  

• specFile: Best for new features or significant refactors.

  Copy"specFile": "specs/new-onboarding-flow.md"
  

Creating Specs with generate-spec

You can use the gemini ralph generate-spec command to help you think through a feature and generate a high-quality markdown spec file.

Copygemini ralph generate-spec "Add a multi-step wizard for project creation"

This command will act as a Senior PM, ask you clarifying questions, and then write a detailed specification to a file in your specs/ directory.

4. Running Ralph

Execute the runner using uv.

Interactive TUI Mode (Default)

Best for monitoring progress in real-time.

Copyuv run scripts/runner-ralph/ralph.py

Key Flags

4. Workflow

When you run Ralph, it follows this cycle:

1. Read PRD: Finds the first incomplete story in prd.json.
2. Git Setup:
   • Ensures working directory is clean.
   • Creates a story branch: ralph/<story-id>.
3. Execution:
   • Generates a prompt combining AGENTS.md, prompt.md, prd.json, and current progress.
   • Runs the Agent CLI (Cursor or Claude).
   • Logs decisions and learnings to worklogs/<story-id>.md.
4. Completion:
   • Agent signals <promise>COMPLETE</promise>.
   • Review (Optional): A "reviewer" agent critiques the code.
   • Merge: Commits changes and merges ralph/<story-id> back to the base branch.
   • Update: Marks story as passed in prd.json.
5. Repeat: Moves to the next story.

5. Troubleshooting

• "Working directory not clean": Commit or stash changes before running. Ralph needs a clean slate to manage branches.
• Agent not found: Ensure the CLI (agent for Cursor, claude for Claude) is in your PATH.
• Stuck loop: Check progress.txt or the specific worklogs/<story-id>.md to see what the agent is struggling with. You may need to refine the story description or add hints to AGENTS.md.

Provider Installation

Gemini CLI

This skill is provider-agnostic but requires a compatible Agent CLI (Cursor or Claude) to perform the actual coding work.

Claude Code

Ensure @anthropic-ai/claude-code is installed globally or available in the environment.

Cursor

Ensure the Cursor CLI is installed. The command is typically agent.