ralph-split

Decompose large GitHub issues into smaller atomic sub-issues with dependencies.

2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cdubiel08/ralph-hero --skill ralph-split
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ralph-split
Source: https://github.com/cdubiel08/ralph-hero/tree/main/plugin/ralph-hero/skills/ralph-split
Command: npx skills add https://github.com/cdubiel08/ralph-hero --skill ralph-split

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill breaks down large, complex GitHub issues (M/L/XL estimates) into smaller, more manageable sub-issues (XS/S estimates) to facilitate atomic implementation and clearer task tracking.

Core Features & Use Cases

  • Issue Decomposition: Splits large tickets into granular sub-tasks.
  • Dependency Management: Establishes blocking relationships between newly created sub-issues.
  • Workflow Integration: Updates parent issue and moves sub-issues to appropriate states.
  • Use Case: You have a large epic to "Implement user authentication." This Skill can break it down into sub-issues like "Create user database schema," "Implement sign-up API endpoint," "Develop login UI component," and "Add password reset functionality," each with clear dependencies.

Quick Start

Use the ralph-split skill to break down issue number 123 into smaller sub-issues.

Frequently Asked Questions about ralph-split

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

FAQPage Schema
How do I break down large GitHub issues into smaller sub-issues?▼

Breaking down large GitHub issues involves analyzing ticket scope to identify natural boundaries, then creating atomic XS/S estimated sub-issues. This Skill establishes blocking dependencies between new child issues and updates the parent issue.

What is epic decomposition in agile task management?▼

Epic decomposition is the process of splitting large agile tickets into granular sub-tasks to facilitate atomic implementation. It establishes blocking dependencies between newly created issues to ensure clearer task tracking and workflow integration.

How do I manage dependencies between sub-issues on GitHub?▼

You manage dependencies between sub-issues by using issue decomposition to establish blocking relationships automatically. The Skill creates child issues from large tickets, sets dependency relationships, and moves sub-issues to appropriate workflow states.

Can I split an existing GitHub issue into atomic tasks without losing scope?▼

You can split existing GitHub issues into atomic tasks while preserving scope. The Skill analyzes the original issue scope, identifies natural boundaries for splitting, and generates smaller XS/S estimated sub-issues with clear dependencies.

When should I decompose GitHub issues into smaller tasks?▼

Decompose GitHub issues into smaller tasks when working with large M/L/XL estimated tickets requiring atomic implementation. Breaking complex epics into XS/S sub-issues with clear dependencies facilitates efficient implementation and clearer task tracking.