breakdown-plan

Generates GitHub project plans with Epic, Feature, Story, and Enabler issue hierarchies.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/hoonsubin/scrum-master-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/scrum-master-mcp-server/tree/main/.roo/skills/breakdown-plan
Command: npx skills add https://github.com/hoonsubin/scrum-master-mcp-server --skill breakdown-plan-hoonsubin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a finished PRD and technical breakdown into a structured, trackable GitHub project plan is slow and error-prone, often resulting in inconsistent issues, missing dependencies, and unclear priorities. ## Core Features & Use Cases - Hierarchical Issue Planning: Produces a complete Epic > Feature > Story/Enabler > Test breakdown with INVEST-compliant stories, acceptance criteria, and Definition of Done. - Dependency and Priority Mapping: Assigns P0-P3 priorities, value tiers, Fibonacci story points, and blocking relationships across all work items. - Automation Templates: Provides GitHub Actions workflows for automated issue creation and status transitions, plus Kanban board and sprint planning configuration. - Use Case: After finishing a feature PRD and technical breakdown, generate a project-plan.md and issues-checklist.md with ready-to-create GitHub issues, estimates, and sprint assignments. ## Quick Start Ask the agent to generate a GitHub project plan with issue breakdown from the PRD and technical breakdown for your feature.

Frequently Asked Questions about breakdown-plan

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

FAQPage Schema
How do I break down a feature PRD into GitHub issues?▼

Provide the feature PRD, technical breakdown, and implementation plan, then generate a project plan that decomposes the work into Epic, Feature, Story, Enabler, and Test issues. Each issue follows a template with acceptance criteria, estimates, and dependency links.

What issue hierarchy should I use for Agile GitHub projects?▼

Use Epic for large business capabilities, Feature for deliverable functionality, Story for user-facing requirements, Enabler for technical infrastructure, and Test for QA work. Stories should follow INVEST criteria and carry Fibonacci story point estimates.

Can I automate GitHub issue creation with GitHub Actions?▼

Yes, the plan includes GitHub Actions workflow templates using actions/github-script to create feature issues from workflow dispatch inputs and to move issues across board columns when pull requests open or merge.

What inputs are required before generating a project plan?▼

You need the feature PRD, technical breakdown, and implementation plan documents completed first. Related planning prompts cover test strategy, architecture, and feature requirements if those artifacts are missing.

How are priorities and estimates assigned to issues?▼

Priorities use a P0-P3 scale combined with high, medium, and low value tiers based on critical path and business impact. Estimates use Fibonacci story points for stories and t-shirt sizes for epics and features.