breakdown-plan

Generate GitHub project plans and structured issues from feature artifacts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mmahalwy/cooper --skill breakdown-plan-mmahalwy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown-plan
Source: https://github.com/mmahalwy/cooper/tree/main/.agents/skills/breakdown-plan
Command: npx skills add https://github.com/mmahalwy/cooper --skill breakdown-plan-mmahalwy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts scattered product artifacts into a structured, actionable GitHub project plan so teams avoid ad-hoc issue creation, missed dependencies, and unclear priorities. It standardizes epics, features, stories, enablers, and tests into repeatable issue templates and Kanban-ready boards for reliable delivery.

Core Features & Use Cases

  • Hierarchical Issue Generation: Produce Epic → Feature → Story/Enabler → Task/Test breakdowns with acceptance criteria and estimates.
  • Dependency Mapping & Prioritization: Identify blocking relationships, assign priority/value labels, and surface the critical path for release planning.
  • Project Board & Automation Guidance: Recommend Kanban columns, custom fields, and example GitHub Actions for automated issue creation and status updates.
  • Use Case: Turn a PRD, technical breakdown, and test plan for a new feature into a project-plan.md and issues-checklist.md and optionally scaffold Issue templates and action workflows for the repo.

Quick Start

Generate a GitHub project plan for epic "search-revamp" and feature "improved-search" that creates epic, feature, story, enabler, and test issues with dependencies, priorities, estimates, and automation notes.

Frequently Asked Questions about breakdown-plan

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

FAQPage Schema
How do I generate GitHub issues from a PRD and technical breakdown?

To generate GitHub issues from a PRD, you need a structured breakdown that converts product artifacts into epics, features, stories, enablers, and tests. This process outputs a project-plan.md and issues-checklist.md with dependencies, priorities, and estimates for Kanban board configuration.

What is the best way to map dependencies and priorities for GitHub project planning?

Mapping dependencies for GitHub project planning involves identifying blocking relationships across issues and assigning priority labels. This surfaces the critical path for release planning and standardizes issue templates to avoid missed dependencies during delivery.

Can I automate GitHub issue creation and status updates with Actions?

Yes, you can automate GitHub issue creation and status updates using GitHub Actions. The planning process provides example workflow snippets and recommends Kanban columns with custom fields to trigger automated issue creation from structured project plans.

Do I need a testing artifact to create a complete GitHub project plan?

Yes, a testing artifact is required alongside a PRD, technical breakdown, and implementation plan to create a complete GitHub project plan. These inputs are necessary to generate test issues with acceptance criteria and structured issue checklists.

How does hierarchical issue generation work for agile epics and stories?

Hierarchical issue generation breaks down work into Epic, Feature, Story, Enabler, and Task categories. Each generated issue includes specific acceptance criteria and estimates, transforming scattered artifacts into a structured, Kanban-ready format for reliable delivery.

What limitations exist when converting product artifacts into GitHub issue templates?

Converting product artifacts into GitHub issue templates requires complete PRD, implementation, and testing inputs to function properly. Without these structured artifacts, the dependency mapping and critical path identification for agile release planning cannot be accurately generated.