breakdown-plan

Generate GitHub project plans with Epic, Feature, Story, and Test hierarchies from feature artifacts.

Updated Mar 30, 2026

Search Tags:#automation #documentation #agile #kanban #breakdown #project-management

Ready to run

npx skills add https://github.com/nashirabbash/autorepychatbot --skill breakdown-plan-nashirabbash

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: breakdown-plan
Source: https://github.com/nashirabbash/autorepychatbot/tree/main/.agents/skills/breakdown-plan
Command: npx skills add https://github.com/nashirabbash/autorepychatbot --skill breakdown-plan-nashirabbash

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform scattered feature artifacts (PRD, UX design, technical breakdown, and testing plan) into a cohesive, hierarchical project plan that can be used to drive GitHub issues and automation.

Core Features & Use Cases

Generate Epic > Feature > Story/Enabler > Test hierarchies from input artifacts.
Create linked issue templates for epic, feature, and story levels with clear acceptance criteria and DoD.
Enable automated tracking and dependency mapping on GitHub projects/boards to streamline planning and execution.

Quick Start

Provide the complete artifact bundle (PRD, UX design, technical breakdown, testing plan) and run the prompt to generate a fully wired GitHub project plan with issue templates and board configuration.

Frequently Asked Questions about breakdown-plan

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

FAQPage Schema

How do I generate a hierarchical GitHub project plan from PRD and UX design artifacts?▼

To generate a hierarchical GitHub project plan from PRD and UX design artifacts, provide your complete artifact bundle including technical breakdown and testing plans. The tool processes these inputs to automatically create Epic, Feature, Story, and Test hierarchies with linked issues and dependency mappings.

What is the best way to automate Kanban board configuration and issue creation for Agile projects?▼

Automating Kanban board configuration and issue creation involves using feature artifacts to generate structured issue templates and board setups. This approach applies dependency mapping and priority assignment directly to your GitHub projects, streamlining Agile planning and execution tracking.

Can I map dependencies and assign priorities across Epic, Feature, and Story levels in GitHub?▼

Yes, you can map dependencies and assign priorities across Epic, Feature, and Story levels in GitHub. The automation processes your testing plan and technical breakdown to establish clear acceptance criteria, Definition of Done, and linked issue structures for each hierarchy tier.

Do I need a complete testing plan and technical breakdown to automate Agile issue structures?▼

You need a complete artifact bundle including the PRD, UX design, technical breakdown, and testing plan to automate Agile issue structures effectively. Providing the full set of feature artifacts ensures the generated project plan has accurate dependency mappings and comprehensive hierarchical tracking.

How does automated Epic to Task breakdown handle acceptance criteria and Definition of Done?▼

Automated Epic to Task breakdown handles acceptance criteria and Definition of Done by extracting requirements from your input artifacts and embedding them directly into linked issue templates. This ensures every generated Story, Enabler, and Test issue maintains clear quality standards for execution.