ralph

Loop task execution until architect verification confirms full completion.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill ralph-kyrie66nb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.agents/skills/ralph
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill ralph-kyrie66nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralph provides a persistent, self-correcting loop that continues work on a task until it is fully completed and architect-verified, reducing partial results and missed edge cases.

Core Features & Use Cases

  • Persistence across retries to ensure completion
  • Parallel delegation to specialists with guided verification
  • Architect sign-off required before final completion, with stateful iteration tracking

Quick Start

Initiate a Ralph iteration and let it persist until completion with verification.

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I automate task completion verification for multi-step agent orchestration?

Agent orchestration uses a self-correcting loop that persists iteration state and delegates parallel tasks to specialists, requiring formal architect sign-off before declaring any task fully completed.

What's the best way to ensure multi-iteration tasks persist until fully completed?

Best way to ensure multi-iteration task persistence is using a self-correcting loop that tracks stateful iterations across retries, requiring architect sign-off before final completion to reduce partial results.

Can I use parallel delegation for sub-agents during task automation?

Parallel delegation coordinates parallel sub-agents during task automation, applying guided verification to specialist outputs and enforcing architect sign-off before declaring final completion.

Does state management work across retries when task automation fails?

State management persists iteration state across retries, allowing the self-correcting loop to resume work automatically until the task reaches full completion and architect verification.

Why does my automated task return partial results instead of completing fully?

Partial results occur when tasks lack a persistent verification loop; enforcing architect sign-off and stateful iteration tracking ensures the task continues iterating until fully complete.

When do I need formal architect verification in an automation loop?

Formal architect verification is needed before declaring final completion in an automation loop, ensuring all edge cases are handled and partial results are eliminated through guided sign-off.