ralph

Splits GitHub issues into independently runnable Ralph stories in prd.json.

1|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/taxmaxi/taxmaxi --skill ralph-taxmaxi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ralph
Source: https://github.com/taxmaxi/taxmaxi/tree/main/.agents/skills/ralph
Command: npx skills add https://github.com/taxmaxi/taxmaxi --skill ralph-taxmaxi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually breaking a GitHub planning or implementation issue into small, executable tasks for an autonomous coding loop is error-prone and inconsistent. This Skill fetches the issue, records its context in ralph/intake.md, and writes structured, dependency-ordered stories into ralph/prd.json. ## Core Features & Use Cases - Issue Import: Fetches a GitHub issue with gh CLI, including parent issue context and sibling issue titles, and records parsed sections in ralph/intake.md. - Story Splitting: Converts issue templates (to-prd, to-issues, request-refactor-plan, triage-issue) into multiple small, independently verifiable Ralph stories with acceptance criteria, priorities, and verification commands. - Dependency Management: Uses blocked_by for Ralph story ordering and blocked_by_issues for GitHub issue blockers, with deduplication against existing stories. - Use Case: A maintainer has a triage-issue describing a bug with a TDD fix plan. The Skill splits it into RED/GREEN cycle stories in prd.json so the Ralph loop can execute them one at a time. ## Quick Start Import GitHub issue number 123 into Ralph by splitting it into stories in ralph/prd.json.

Frequently Asked Questions about ralph

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

FAQPage Schema
How do I import a GitHub issue into Ralph prd.json?▼

Ask the agent to import the issue by number or URL. The Skill fetches it with gh issue view, writes ralph/intake.md with parsed sections, then splits the issue into multiple stories in ralph/prd.json with acceptance criteria and verification commands.

How does Ralph split an issue into stories?▼

It splits on independently verifiable units already in the issue: user story clusters, acceptance criteria groups, refactor commit steps, or RED/GREEN cycles. Each story stays a complete vertical slice, and blocked_by links order dependent stories.

Which issue templates does the Ralph skill support?▼

It recognizes four templates: to-prd, to-issues, request-refactor-plan, and triage-issue. Each template has specific section detection and splitting rules, such as one story per commit step for refactor plans or per RED/GREEN cycle for triage plans.

Does the Ralph skill work with parent and sibling GitHub issues?▼

Yes. When the source issue names a parent, it fetches the parent and lists sibling issues mentioning the same parent. Sibling titles are recorded in intake.md as future-work context but no stories are created for them.

What are the limitations of Ralph story splitting?▼

It will not split a vertical slice into horizontal layers like schema-only or UI-only stories, and it avoids creating stories for out-of-scope work. A single story is kept only when the issue is already one small verifiable slice.