breakdown-plan

Generate GitHub issues from Epic, Feature, Story, Enabler, and Test hierarchies.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/hoonsubin/github-projects-mcp-server --skill breakdown-plan-hoonsubin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown-plan
Source: https://github.com/hoonsubin/github-projects-mcp-server/tree/main/.roo/skills/breakdown-plan
Command: npx skills add https://github.com/hoonsubin/github-projects-mcp-server --skill breakdown-plan-hoonsubin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the complexity of planning and automating issue creation for project management, providing a structured and efficient way to organize projects and manage work items.

Core Features & Use Cases

  • Comprehensive Project Planning: Generates detailed project plans with Epic > Feature > Story/Enabler > Test hierarchy, including dependencies and priorities.
  • Automated Issue Creation: Automatically creates issues in GitHub with all necessary information and templates.
  • Integration with GitHub Projects: Seamlessly integrates with GitHub Projects to facilitate Kanban-style tracking and issue management.
  • Use Case: A Project Manager uses this Skill to plan a new project, creating an epic, features, stories, enablers, and tests, which automatically generate GitHub issues and are ready for Kanban board configuration.

Quick Start

Generate a comprehensive project plan for a new feature with the breakdown-plan skill and GitHub Issues by providing the epic name and feature name.

Frequently Asked Questions about breakdown-plan

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

FAQPage Schema
How do I automate GitHub issue creation for Agile project planning?

You can automate GitHub issue creation by generating a comprehensive project plan with an Epic, Feature, Story, and Test hierarchy, which automatically creates issues ready for Kanban tracking.

What's the best way to structure GitHub issues for Agile methodology?

The best way to structure GitHub issues is using a hierarchical breakdown from Epic to Feature, then to Story or Enabler, and finally Test, including all necessary dependencies and priorities.

Does this project planning approach support GitHub Projects Kanban boards?

Yes, the automated issue planning seamlessly integrates with GitHub Projects, allowing you to facilitate Kanban-style tracking and manage your generated issues directly on the board.

Can I use automated issue planning for software development tasks outside of standard coding?

Yes, you can use this automated issue planning for software development and any other projects that utilize GitHub for issue tracking and require structured Agile project management.

Do I need prior Agile methodology knowledge to use automated issue breakdown?

Yes, you need existing knowledge of Agile methodology and GitHub issue tracking features to effectively utilize the automated issue breakdown and project planning capabilities.