ralph-loop

Dispatch repository-wide or design-doc-specific Ralph tasks with injected runtime context for Codex or Claude.

6|3|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/jamesaphoenix/tx --skill ralph-loop-jamesaphoenix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-loop
Source: https://github.com/jamesaphoenix/tx/tree/main/.claude/skills/ralph-loop
Command: npx skills add https://github.com/jamesaphoenix/tx --skill ralph-loop-jamesaphoenix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ralph Loop orchestrates task dispatch by running Ralph against either the full repository queue or a single design doc, injecting current task context, linked design-doc content, and scope information for Codex or Claude runtimes.

Core Features & Use Cases

  • Global-queue and design-doc scoped dispatch with injected task, spec, and queue context.
  • Ensures deterministic task selection, design-doc linkage, and runtime-specific messaging for agents.
  • Use Case: Coordinate large-scale workflows where multiple tasks share a design doc and require synchronized state across runtimes.

Quick Start

Run Ralph with ./scripts/ralph.sh --all-tasks to dispatch the full queue or with ./scripts/ralph.sh --design-doc <name> to scope to a single design doc.

Frequently Asked Questions about ralph-loop

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

FAQPage Schema
How do I automate task dispatch from a design doc to Codex or Claude runtimes?

Task dispatch to Codex or Claude runtimes is automated by running the ralph.sh script with the --design-doc flag, which injects the current task JSON, linked design-doc markdown, and full scope context into the agent runtime for deterministic execution.

What is the best way to orchestrate a full repository task queue for automated execution?

Orchestrating a full repository task queue is handled by executing the ralph.sh script with the --all-tasks flag, which dispatches the entire queue while injecting task, spec, and queue context for the target runtime.

Can I scope automated task execution to a single design doc instead of the whole queue?

Yes, you can scope task execution to a single design doc by passing the --design-doc flag with the doc name to the ralph.sh script, ensuring only tasks linked to that design doc are dispatched.

Do I need any specific dependencies or environment setup to run Ralph loops?

Ralph loops require the scripts/ralph.sh utility to be present in your repository environment, but no external dependencies are needed beyond the script itself to dispatch tasks to Codex or Claude runtimes.

Why use design-doc scoped task dispatch instead of running tasks individually?

Design-doc scoped task dispatch ensures synchronized state across multiple tasks sharing the same design doc, providing deterministic task selection and runtime-specific context injection that individual task execution cannot achieve.

What context information gets injected when dispatching tasks through Ralph loops?

Ralph loops inject the current task JSON, linked design-doc markdown content, and the full queue scope into the Codex or Claude runtime, ensuring the agent has complete deterministic context for automated execution.