ralph

Process queued HTML tickets through todo, inprogress, and done folders.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/zerwiz/wayofpi --skill ralph-zerwiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/zerwiz/wayofpi/tree/main/.pi/skills/ralph
Command: npx skills add https://github.com/zerwiz/wayofpi --skill ralph-zerwiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralph turns a folder-based HTML request queue into a predictable one-ticket-at-a-time workflow, reducing mistakes when multiple tasks, states, and handoffs need to be managed carefully.

Core Features & Use Cases

  • Queue-driven execution: Checks todo, inprogress, and done folders to pick the next ticket and advance it through the workflow.
  • Single-file focus: Ensures only the ticket-defined HTML file is created or edited, preventing unrelated changes.
  • Operational handoff: Supports controlled batch work for HTML updates, ticket processing, and agent-assisted delegation when a task needs escalation.

Quick Start

Use the ralph skill to process the next ticket in the queue, complete the assigned HTML file exactly as instructed, and move the ticket to done.

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I process HTML tickets one at a time from a folder queue?

You can process HTML tickets by moving them through todo, inprogress, and done folders using a queue-driven workflow that handles one ticket per turn to ensure controlled execution and prevent unrelated file changes.

What is the best way to automate batch HTML file generation from a ticket queue?

Automating batch HTML file generation requires a SKILL.md-driven queue protocol that transitions tickets between folder states, ensuring only the ticket-defined HTML file is created or updated during each working turn.

How does directory-based ticket processing prevent mistakes in HTML workflows?

Directory-based ticket processing prevents mistakes by enforcing exclusive target-file editing and explicit folder state transitions, ensuring deterministic execution of one HTML task at a time without unrelated changes.

Can I use folder state transitions for agent-assisted HTML task delegation?

Folder state transitions support agent-assisted delegation by moving HTML tickets from todo to inprogress to done, providing a controlled batch workflow for tasks that need escalation or careful handoff management.

Do I need a specific folder structure to queue HTML tickets for automated processing?

You need a working directory with todo, inprogress, and done folders to queue HTML tickets, along with a mandatory SKILL.md file that defines the queue protocol for deterministic ticket processing.

Why does my HTML ticket queue workflow require single-file focus during execution?

Single-file focus is required to ensure only the ticket-defined HTML file is created or edited, preventing unrelated changes and maintaining deterministic execution across the batch workflow directory.