ralph

Orchestrate queue-based task processing with isolated subagents per phase.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/lightningfastsls/London_Lab --skill ralph-lightningfastsls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/lightningfastsls/London_Lab/tree/main/.claude/skills/ralph
Command: npx skills add https://github.com/lightningfastsls/London_Lab --skill ralph-lightningfastsls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Queue processing with context isolation across tasks requires fresh subagent contexts to prevent contamination and data leakage.

Core Features & Use Cases

  • Isolates each phase with a dedicated subagent to preserve clean state.
  • Supports serial, parallel, batch-filter, and dry-run processing modes for flexible workloads.
  • Triggers on chat commands like "/ralph" or "ralph N" to integrate with conversational workflows.

Quick Start

Process N tasks from the queue with fresh context per phase, selecting a mode and optional filters as needed.

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I process queued tasks with isolated subagents to prevent context contamination?

Queue processing with isolated subagents prevents context contamination by assigning a dedicated subagent with fresh context to each task phase, ensuring deterministic handling and clean separation between tasks.

Can I run queue-driven workloads in parallel and batch modes?

Yes, queue-driven workloads support serial, parallel, batch-filter, and dry-run processing modes, allowing flexible orchestration of tasks while maintaining strict context isolation across all operations.

Why does cross-task context leakage happen during task orchestration?

Cross-task context leakage happens when subagents share state across processing phases; isolating each phase with a dedicated subagent using fresh context prevents data contamination and ensures deterministic task handling.

How do I trigger queue processing from a chat command?

You can trigger queue processing by using chat commands like "/ralph" or "ralph N" to process N tasks from the queue, selecting a processing mode and applying optional filters as needed.

When should I use dry-run mode for task processing?

Dry-run mode should be used when you need to validate queue-driven task processing logic and orchestration without executing side effects, ensuring deterministic task handling before committing to full execution.