Split large GitHub issues into scoped sub-issues with dependencies and acceptance criteria.
npx skills add https://github.com/ousiass/dotfiles --skill issue-split
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
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.
gh, then appends an ordered checklist back to the parent issue.Run the issue-split skill with an issue number, for example: “/issue-split #123”.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
richkuoAggregate GitHub milestone issue data into a structured markdown table.
tomoasleepCreate, list, and remove GitHub Sub Issues under a parent issue.
hylarucoderDefine and refine product requirements by drafting and auditing PRDs.
AustinZ21Convert dependency-ordered spec-kit tasks into GitHub issues.