skills.rest
pcortes
pcortesCOMMUNITY
Explore all skills by this author →
GitHub

issue-splitter

Split complex GitHub issues into 2-4 implementable sub-issues.

Updated Aug 27, 2026
Search Tags:#automation#planning#acceptance criteria#split#issues#sub-issues
One-click install
npx skills add https://github.com/pcortes/swarm-attack --skill issue-splitter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-splitter
Source: https://github.com/pcortes/swarm-attack/tree/main/swarm_attack/skills/issue-splitter
Command: npx skills add https://github.com/pcortes/swarm-attack --skill issue-splitter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Split complex GitHub issues into smaller, implementable sub-issues.

Core Features & Use Cases

  • Splitting strategies: by layer, by operation, by acceptance criteria, by phase.
  • Sub-issue packaging: 3-5 acceptance criteria per sub-issue, clear scope.

Quick Start

Provide a complex issue with title, body, and acceptance criteria; returns 2-4 sub-issues with focused scopes.

Frequently Asked Questions about issue-splitter

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

FAQPage Schema
How do I split a complex GitHub issue into smaller sub-issues?▼

Split complex issues by breaking them into 2-4 focused sub-issues using layer, operation, acceptance-criteria, or phase strategies. Each sub-issue receives 3-5 acceptance criteria, a clear title, and structured body sections (Description and Acceptance Criteria), sized as small or medium work.

When should I split an issue into sub-issues instead of keeping it whole?▼

Split issues when they exceed 12 acceptance criteria or 8 methods, indicating complexity too large for a single implementation. Breaking them into independent sub-issues improves clarity, enables parallel work, and reduces delivery risk.

What splitting strategies work best for different issue types?▼

Use layer-based splitting for architectural concerns, operation-based for distinct workflows, acceptance-criteria-based for feature groups, and phase-based for sequential dependencies. Choose the strategy matching your issue's natural structure.

Can I use issue splitting with existing GitHub workflows?▼

Yes. Issue splitting generates standard GitHub sub-issues with titles, descriptions, and acceptance criteria that integrate directly into your existing tracking, planning, and automation workflows without special setup.

What happens if my issue doesn't meet the complexity threshold?▼

Issues under 12 acceptance criteria or 8 methods are already scoped appropriately and don't require splitting. Splitting works best for complex issues; simpler ones proceed more efficiently as single tasks.

How detailed should acceptance criteria be in the generated sub-issues?▼

Each sub-issue includes 3-5 acceptance criteria that define concrete, testable outcomes. Criteria focus the scope, enable parallel development, and make completion measurable without overcomplicating smaller work.

Related Skills

Explore More Software Engineering Skills→
zxkanezxkane
33

create-issue

Create structured GitHub issues with templates and attached workspace changes.

Community
Advanced
oletizioletizi

feature-issues

Create GitHub parent and per-phase issues from completed workplans.

Community
Intermediate
shiimanshiiman
2

issue-list

List open GitHub issues sorted by priority labels.

Community
Intermediate
ShubhamsabooShubhamsaboo
131.7k

project-planner

Break down complex projects into tasks with timelines and milestones.

Community
Basic