issue-splitter

Classify issue packets into keep, split, defer, or blocked scopes.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill issue-splitter-danielbaustin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-splitter
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/issue-splitter
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill issue-splitter-danielbaustin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Classify whether one issue should stay intact, split into bounded follow-ons, defer splitting, or stop for operator judgment, while preserving issue-graph and card truth.

Core Features & Use Cases

  • Inspect one issue packet for mixed or drifting scope.
  • Detect concern buckets that may deserve separate follow-on issues.
  • Recommend whether to keep the issue intact, split now, defer, or block, preserving rationale and issue-graph notes.
  • Narrow the current issue scope in recommendations without mutating the tracker.
  • Does not mutate tracker items, rewrite milestones, or perform implementation work.

Quick Start

Feed the current issue packet or task bundle to the issue-splitter planner and review the emitted classification and proposed follow-ons.

Frequently Asked Questions about issue-splitter

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

FAQPage Schema
How do I know if an issue needs splitting or should stay as-is?

Issue splitting decisions are made by analyzing source prompts and task bundle metadata to classify scope as keep_as_is, split_now, defer, or blocked. The planner detects mixed concerns and evaluates whether bounded follow-on issues are needed.

What is issue scope classification in project management?

Issue scope classification evaluates a task bundle to determine if it contains drifting or mixed scope, then recommends keeping it intact, splitting into bounded follow-ons, deferring, or blocking for operator judgment.

How do I split a large task bundle into follow-on issues without mutating the tracker?

To split a task bundle safely, feed the issue packet to the planner which proposes follow-on scopes and narrows current issue scope in recommendations without mutating tracker items or rewriting milestones.

Can I assess project risk and traceability when planning issue splits?

Yes, the planner enforces policy requirements and preserves issue-graph notes to maintain traceability, outputting a structured contract with classification, rationale, and recommended handoff for risk assessment.

Does issue splitting work with existing issue packets and task bundles?

Yes, it scopes inputs from a given issue packet or task bundle by analyzing repo_root, mode, and target parameters to process source prompts and structured markdown files for safe classification.

When should I avoid splitting an issue into follow-ons?

You should avoid splitting when the planner classifies the issue as blocked, requiring operator judgment, or defer when scope is not yet mixed enough to warrant bounded follow-on issues.