issue-split

Split large GitHub issues into scoped sub-issues with dependencies and acceptance criteria.

Updated May 3, 2026

Search Tags:#github #gh cli #sub-issues #spec extraction #dependency planning #issue splitting #interactive drafting

Ready to run

npx skills add https://github.com/ousiass/dotfiles --skill issue-split

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-split
Source: https://github.com/ousiass/dotfiles/tree/main/.claude/skills/issue-split
Command: npx skills add https://github.com/ousiass/dotfiles --skill issue-split

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you break a large GitHub Issue into smaller, implementable sub-issues, with the right scope, dependencies, and acceptance criteria so development can start immediately without confusion.

Core Features & Use Cases

Interactive scope splitting: Proposes scope-based sub-issues (and dependency order) and iteratively confirms the split with the user.
Spec-accurate drafting: Copies the relevant parts of linked spec documents into each sub-issue using “要点＋該当セクション全文の引用” to prevent requirement drift.
Sub-issue creation and linking: Creates sub-issues via gh, then appends an ordered checklist back to the parent issue.

Quick Start

Run the issue-split skill with an issue number, for example: “/issue-split #123”.

Frequently Asked Questions about issue-split

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

FAQPage Schema

How do I split a large GitHub issue into smaller sub-issues?▼

To split a large GitHub issue, you interactively draft scope-based sub-issues with correct dependencies and acceptance criteria. The process requires user approval before creating sub-issues via GitHub CLI and linking them back to the parent.

How do I create sub-issues with correct dependencies and acceptance criteria?▼

You create sub-issues with correct dependencies by interactively splitting the parent issue's scope. The system drafts sub-issues containing relevant spec document quotes and acceptance criteria, then creates them using GitHub CLI after user approval.

Does issue splitting work with linked spec markdown files?▼

Yes, issue splitting works with linked spec markdown files by extracting relevant sections. It copies applicable spec content into each sub-issue using point summaries and full section quotes to prevent requirement drift during implementation.

Can I use GitHub CLI to fetch and create sub-issues automatically?▼

You can use GitHub CLI to fetch parent issue data and create sub-issues. After interactively drafting and confirming the split scope, the system creates sub-issues via `gh` commands and appends an ordered checklist back to the parent issue.

What is the best way to turn spec-generated requirements into a development plan?▼

The best way to turn spec-generated requirements into a development plan is scope-based issue splitting. It breaks down requirements across backend, frontend, CI/test, and setup workstreams into implementation-ready sub-issues with defined dependency orders.

Do I need to approve sub-issue creation before it modifies my GitHub repository?▼

Yes, user approval is required before creating or modifying issue contents. The interactive drafting process proposes the sub-issue scope, dependencies, and acceptance criteria, ensuring you maintain control over repository changes.