break-down-epic

Name: break-down-epic
Availability: InStock
Author: TypeMD

Break down GitHub epic issues into sub-issues via GitHub CLI.

9|2|Updated Mar 4, 2026

Search Tags:#automation #github #cli #epic #breakdown #subissues

Ready to run

npx skills add https://github.com/typemd/typemd --skill break-down-epic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: break-down-epic
Source: https://github.com/typemd/typemd/tree/main/.claude/skills/break-down-epic
Command: npx skills add https://github.com/typemd/typemd --skill break-down-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large GitHub epic issues often contain many planned features that need to be split into smaller, trackable sub‑issues. Managing this manually is time‑consuming and error‑prone.

Core Features & Use Cases

Epic Analysis: Reads the epic, validates its type, and extracts the “Planned Features” section.
Sub‑Issue Drafting: Generates titles, types, labels, bodies, and parent linkage for each feature.
User Confirmation Loop: Presents a full breakdown for review, allowing edits before creation.
Automated Creation: Uses GitHub CLI and GraphQL to create sub‑issues sequentially, preserving order and optional blocking relationships.
Reporting: Returns a summary table with issue numbers and URLs.

Quick Start

Ask the skill to break down epic #123 into sub‑issues.

Frequently Asked Questions about break-down-epic

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

FAQPage Schema

How do I break down a GitHub epic into sub-issues automatically?▼

To break down a GitHub epic into sub-issues, this skill parses the epic issue metadata, extracts the Planned Features section, drafts individual issues with labels, and uses GitHub CLI to create sub-issues sequentially while preserving parent linkage and optional blocking relationships.

What is the best way to split large GitHub epics into trackable issues?▼

The best way to split large GitHub epics is to parse the epic body for planned features, generate sub-issue drafts with titles and types, and execute automated GitHub CLI commands to create linked sub-issues, eliminating manual entry errors and saving time.

Do I need GitHub CLI installed to create sub-issues from an epic?▼

Yes, you need GitHub CLI access installed and configured. The skill requires GitHub CLI and GraphQL to create sub-issues sequentially on your repository, parse issue metadata, and apply optional labels and dependency handling.

Can I review and edit sub-issues before they are created on GitHub?▼

Yes, you can review and edit sub-issues before creation. The skill presents a full breakdown of drafted sub-issues for user confirmation in a review loop, allowing you to make edits before executing GitHub CLI commands to create them.

How does automated epic breakdown handle dependencies between sub-issues?▼

Automated epic breakdown handles dependencies by applying optional blocking relationships during creation. It uses GitHub CLI and GraphQL to create sub-issues sequentially, preserving the planned order and linking issues to the parent epic.

Why does splitting a GitHub epic manually lead to tracking errors?▼

Splitting a GitHub epic manually leads to tracking errors because large epics contain many planned features that require individual sub-issues. Manual management is time-consuming and error-prone, making automated extraction and sequential creation more reliable.