breakdown-plan

Generate GitHub project plans and issue checklists from feature artifacts.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill breakdown-plan-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown-plan
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/breakdown-plan
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill breakdown-plan-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects often lack consistent, traceable issue hierarchies, automated tracking, and clear dependencies, making releases unpredictable and planning time-consuming. This Skill consolidates PRDs, technical breakdowns, implementation plans, and test plans into a single, reproducible GitHub project plan and issue set so teams can move from specification to execution faster.

Core Features & Use Cases

  • Structured Work Hierarchy: Produces Epic > Feature > Story/Enabler > Task/Test breakdowns and templates for each issue level.
  • Automated Issue Guidance: Generates acceptance criteria, labels, estimates, priorities, dependencies, and project-board configurations for Kanban workflows.
  • DevOps Automation Examples: Provides example GitHub Actions snippets for creating issues and updating project-board columns based on PR and issue events.
  • Use Case: Turn a completed feature PRD plus technical and testing documents in docs/ways-of-work/plan into a project-plan.md and issues-checklist.md and a linked set of GitHub issues ready for assignment.

Quick Start

Generate a complete GitHub project plan and create linked issues for a feature using the PRD, technical-breakdown, and implementation-plan files under docs/ways-of-work/plan/{epic-name}/{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 generate a GitHub project plan and create issues from a PRD?

To generate a GitHub project plan, apply this automation to feature-level PRDs, technical breakdowns, and testing documents. It produces structured Markdown project plans and issue checklists, creating linked Epic, Feature, Story, Task, and Test issues with dependencies.

What is the best way to automate GitHub issue creation for agile project planning?

Automating GitHub issue creation for agile planning involves parsing feature artifacts to generate a hierarchical issue set. This Skill outputs a project-plan.md and issues-checklist.md, assigns labels, links dependencies, and provides example GitHub Actions workflow snippets for board updates.

Can I use a technical breakdown document to create a Kanban board with linked dependencies?

Yes, you can use technical breakdown documents to generate Kanban workflows. The Skill processes implementation plans to produce structured issue hierarchies, suggests priorities and estimates, and provides project-board configurations for automated tracking.

Does this GitHub project planning automation work with existing implementation plan files?

Yes, this GitHub project planning automation works with existing implementation plan files stored in your repository docs. It consolidates PRDs and technical documents from your specified docs directory to produce a reproducible project plan and linked issue set.

How does automated issue generation handle agile story and enabler templates?

Automated issue generation handles agile templates by producing Epic, Feature, Story, Enabler, Task, and Test breakdowns. It generates specific templates for each issue level, complete with acceptance criteria, labels, estimates, and linked dependencies for traceability.