breakdown-plan

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

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill breakdown-plan-ultraviollettnympho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown-plan
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/breakdown-plan
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill breakdown-plan-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Breaking down a feature into trackable GitHub issues with proper hierarchy, dependencies, and priorities is time-consuming and inconsistent across teams. This Skill turns PRDs, technical breakdowns, and implementation plans into a structured project plan with ready-to-use issue templates and automation guidance. ## Core Features & Use Cases - Work Item Hierarchy: Generates Epic > Feature > Story/Enabler > Task/Test breakdowns following INVEST criteria and Agile best practices. - Issue Templates: Provides ready-made GitHub issue templates for epics, features, user stories, and technical enablers with acceptance criteria and Definition of Done. - Prioritization & Estimation: Includes a priority/value matrix, Fibonacci story points, and t-shirt sizing guidelines. - Automation Guidance: Supplies GitHub Actions YAML examples for automated issue creation and status updates, plus Kanban board configuration. - Use Case: After finishing a feature PRD and technical breakdown, use this Skill to produce a project-plan.md and issues-checklist.md so the team can create and track all GitHub issues consistently. ## Quick Start Ask the AI to generate a GitHub project plan with an Epic, Feature, Story, and Enabler issue breakdown from your feature PRD and technical breakdown documents.

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 into GitHub issues?

Start from the feature PRD and technical breakdown, then decompose into an Epic containing Features, which split into user Stories and technical Enablers. Each story gets tasks and tests, with acceptance criteria, estimates, and dependency links between issues.

What is the difference between an Epic, Feature, and Story in GitHub?

An Epic is a large business capability spanning multiple features, a Feature is deliverable user-facing functionality within an epic, and a Story is an independently valuable user requirement. Enablers are technical infrastructure work supporting stories.

How do I automate GitHub issue creation with Actions?

Use a workflow_dispatch GitHub Actions workflow with actions/github-script to call the issues.create API. The skill provides YAML examples that create feature issues linked to an epic and update project board status on pull request events.

What inputs does this planning workflow require?

It requires a feature PRD, a technical breakdown, and an implementation plan located under the docs/ways-of-work/plan directory. Without these artifacts, the generated issue breakdown will lack acceptance criteria and dependency detail.

How should story points and estimates be assigned?

Use the Fibonacci scale for stories, where 1 point is under four hours and 8 points is one to two weeks. Epics and features use t-shirt sizes from XS to XL, and anything above 13 points should be broken down further.