ralph

Execute tasks persistently until architect verification confirms completion.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/tuandzung/flink-k8s-ui --skill ralph-tuandzung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/tuandzung/flink-k8s-ui/tree/main/.codex/skills/ralph
Command: npx skills add https://github.com/tuandzung/flink-k8s-ui --skill ralph-tuandzung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Ralph skill addresses the challenge of task completion by creating a persistent loop that works on a task until it is fully completed and architect-verified.

Core Features & Use Cases

  • Persistent Loop: Keeps working on a task until it is completely finished and verified.
  • Parallel Execution: Utilizes parallel execution with session persistence across multiple iterations.
  • Architect Verification: Includes a tiered architect review to ensure quality before task completion.
  • Use Case: Ideal for complex tasks requiring guarantees of completion with thorough verification, like implementing critical software changes or large documentation projects.

Quick Start

Execute 'ralph' with the task you need to complete and verification to be done by an architect.

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I ensure task completion and verification for complex software changes?

To ensure task completion and verification, you can use a persistent execution loop that continuously processes tasks until an architect provides sign-off for quality control.

What is the best way to manage parallel processing with session persistence?

Managing parallel processing with session persistence involves utilizing an execution loop that maintains session state across multiple iterations, ensuring tasks resume and complete without losing progress.

How does architect verification work in a persistent task execution loop?

Architect verification in a persistent task execution loop requires mandatory tiered review by an architect, ensuring quality control standards are met before a task is officially marked as complete.

Can I use parallel execution for large documentation projects requiring guaranteed completion?

Yes, parallel execution is ideal for large documentation projects requiring guaranteed completion, as it processes tasks concurrently while maintaining session persistence across iterations until verified.

Why does my task execution loop stop before reaching architect sign-off?

A task execution loop stops before architect sign-off if the persistent loop mechanism is interrupted or if the mandatory architect review identifies quality control issues requiring further iterations.