ralph

Name: ralph
Availability: InStock
Author: Morgan

Process pending queue tasks via the /process command with persisted status transitions.

Updated Aug 27, 2026

Search Tags:#compatibility #orchestration #queue #task-management #ralph #/process

Ready to run

npx skills add https://github.com/hellofrommorgan/intent-computer --skill ralph-hellofrommorgan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/hellofrommorgan/intent-computer/tree/main/packages/plugin/src/skill-sources/ralph
Command: npx skills add https://github.com/hellofrommorgan/intent-computer --skill ralph-hellofrommorgan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This artifact preserves compatibility for the /process queue contract, ensuring existing orchestration workflows continue to operate during migration.

Core Features & Use Cases

Accept /process as the queue executor command.
Process pending queue tasks one phase at a time.
Persist queue status transitions after each task.
Return explicit success/failure results.
Never invoke nested Task-tool subagents from this skill source.

Quick Start

Invoke the /process command to run queued tasks and manage the queue.

Frequently Asked Questions about ralph

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

FAQPage Schema

How do I process pending queue tasks without invoking nested subagents?▼

To process pending queue tasks without nested subagents, use the /process command to execute queued tasks one phase at a time. This approach ensures deterministic task progression and explicitly returns success or failure results without creating subagent dependencies.

What is the /process queue contract for legacy task orchestration?▼

The /process queue contract is a runtime orchestration mechanism that resolves pending tasks phase by phase. It preserves compatibility for legacy workflows by persisting status transitions after each task completes, ensuring deterministic progression and explicit results.

How do I maintain queue orchestration compatibility during system migration?▼

To maintain queue orchestration compatibility during migration, invoke the /process command as the queue executor. This preserves existing orchestration workflows by processing tasks sequentially and persisting status transitions, allowing legacy tasks to continue operating.

Does the /process queue executor persist task status transitions after each phase?▼

Yes, the /process queue executor persists queue status transitions after each task completes. This deterministic task progression ensures that the queue state is saved between phases, preventing data loss and maintaining explicit success or failure results.

Why does my queue orchestration workflow need deterministic task progression?▼

Queue orchestration needs deterministic task progression to ensure predictable execution and persistent status tracking. Processing pending tasks one phase at a time through /process prevents race conditions, returns explicit results, and avoids nested subagent invocation.

Can I use /process for runtime orchestration in environments with legacy tasks?▼

Yes, /process is applicable in environments relying on the /process queue contract for runtime orchestration and compatibility with legacy tasks. It accepts /process as the queue executor command and processes pending tasks without invoking nested subagents.