ralph-loop

Coordinate multi-agent task execution with durable state and review gates.

92|7|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/dannys-code-corner/incan --skill ralph-loop-dannys-code-corner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-loop
Source: https://github.com/dannys-code-corner/incan/tree/main/.agents/skills/ralph-loop
Command: npx skills add https://github.com/dannys-code-corner/incan --skill ralph-loop-dannys-code-corner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralph Loop provides a disciplined framework for executing complex, multi-agent tasks end-to-end with durable state, explicit review, and safe work-cycle integration, reducing drift and manual coordination overhead.

Core Features & Use Cases

  • Plan-Do-Check-Act loop per slice with durable state under .agents/state/ralph-loop.
  • Non-overlapping worker worktrees that isolate slices and avoid interference during exploration or RFC work.
  • Built-in review/reporting workflow including review-incan-source-quality checks for Incan-related code and an integrated handoff process to the orchestrator.
  • Use cases include RFC-driven feature implementations, large-scale bugfix iterations, and delegated tasks that require multi-step collaboration and documentation.

Quick Start

Describe a scoped task and let Ralph Loop orchestrate planning, implementation, and review across slices.

Frequently Asked Questions about ralph-loop

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

FAQPage Schema
How do I coordinate multi-agent task execution for large feature implementations?

Multi-agent execution is coordinated by orchestrating end-to-end workflows with non-overlapping slice ownership and durable state under .agents/state/ralph-loop. It manages RFC intake, plan creation, and parallel execution across isolated worker worktrees.

What is the Plan-Do-Check-Act loop for multi-agent orchestration?

The Plan-Do-Check-Act loop for multi-agent orchestration is a durable execution cycle that iterates per slice until blockers are resolved. It integrates explicit review gates and verification steps toward end-to-end completion and release readiness.

How do I prevent interference during parallel agent exploration on the same repository?

Interference during parallel agent exploration is prevented by assigning non-overlapping worker worktrees that isolate slices. This ensures each agent operates independently without drift or conflict during RFC work or bugfix iterations.

Can I use worktrees for delegated multi-step collaboration and documentation?

Yes, worktrees support delegated multi-step collaboration by isolating slice ownership per agent. Durable state artifacts are maintained per slice, enabling structured documentation, integrated handoffs, and explicit review reporting.

What's the best way to add review gates to an automated multi-agent workflow?

The best way to add review gates is by integrating explicit checkpoints within the orchestration loop. Built-in reporting workflows trigger source-quality checks and manage handoffs to the orchestrator before proceeding.

When do I need durable state tracking for multi-agent development loops?

Durable state tracking is needed for multi-agent development loops when executing complex, multi-step tasks end-to-end. It reduces manual coordination overhead and prevents drift by recording per-slice artifacts and progress.