breakdown-plan

Name: breakdown-plan
Author: github

9.1kinstalls4.6kforks

How to install breakdown-plan?

github/awesome-copilot/breakdown-plan

$npx -y skills add github/awesome-copilot --skill breakdown-plan

Installs into the current project.

Summary

Issue Planning and Automation prompt that generates comprehensive project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated tracking.

Files · 1

View on GitHub

SKILL.md

1	# GitHub Issue Planning & Project Automation Prompt
2
3	## Goal
4
5	Act as a senior Project Manager and DevOps specialist with expertise in Agile methodology and GitHub project management. Your task is to take the complete set of feature artifacts (PRD, UX design, technical breakdown, testing plan) and generate a comprehensive GitHub project plan with automated issue creation, dependency linking, priority assignment, and Kanban-style tracking.
6
7	## GitHub Project Management Best Practices
8
9	### Agile Work Item Hierarchy
10
11	- Epic: Large business capability spanning multiple features (milestone level)
12	- Feature: Deliverable user-facing functionality within an epic
13	- Story: User-focused requirement that delivers value independently
14	- Enabler: Technical infrastructure or architectural work supporting stories
15	- Test: Quality assurance work for validating stories and enablers
16	- Task: Implementation-level work breakdown for stories/enablers
17
18	### Project Management Principles
19
20	- INVEST Criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
21	- Definition of Ready: Clear acceptance criteria before work begins
22	- Definition of Done: Quality gates and completion criteria
23	- Dependency Management: Clear blocking relationships and critical path identification
24	- Value-Based Prioritization: Business value vs. effort matrix for decision making
25
26	## Input Requirements
27
28	Before using this prompt, ensure you have the complete testing workflow artifacts:
29
30	### Core Feature Documents
31
32	1. Feature PRD: `/docs/ways-of-work/plan/{epic-name}/{feature-name}.md`
33	2. Technical Breakdown: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md`
34	3. Implementation Plan: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md`
35
36	### Related Planning Prompts
37
38	- Test Planning: Use `plan-test` prompt for comprehensive test strategy, quality assurance planning, and test issue creation
39	- Architecture Planning: Use `plan-epic-arch` prompt for system architecture and technical design
40	- Feature Planning: Use `plan-feature-prd` prompt for detailed feature requirements and specifications
41
42	## Output Format
43
44	Create two primary deliverables:
45
46	1. Project Plan: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md`
47	2. Issue Creation Checklist: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.md`
48
49	### Project Plan Structure
50
51	#### 1. Project Overview
52
53	- Feature Summary: Brief description and business value
54	- Success Criteria: Measurable outcomes and KPIs
55	- Key Milestones: Breakdown of major deliverables without timelines
56	- Risk Assessment: Potential blockers and mitigation strategies
57
58	#### 2. Work Item Hierarchy
59
60	```mermaid
61	graph TD
62	A[Epic: {Epic Name}] --> B[Feature: {Feature Name}]
63	B --> C[Story 1: {User Story}]
64	B --> D[Story 2: {User Story}]
65	B --> E[Enabler 1: {Technical Work}]
66	B --> F[Enabler 2: {Infrastructure}]
67
68	C --> G[Task: Frontend Implementation]
69	C --> H[Task: API Integration]
70	C --> I[Test: E2E Scenarios]
71
72	D --> J[Task: Component Development]
73	D --> K[Task: State Management]
74	D --> L[Test: Unit Tests]
75
76	E --> M[Task: Database Schema]
77	E --> N[Task: Migration Scripts]
78
79	F --> O[Task: CI/CD Pipeline]
80	F --> P[Task: Monitoring Setup]
81	```
82
83	#### 3. GitHub Issues Breakdown
84
85	##### Epic Issue Template
86
87	```markdown
88	# Epic: {Epic Name}
89
90	## Epic Description
91
92	{Epic summary from PRD}
93
94	## Business Value
95
96	- Primary Goal: {Main business objective}
97	- Success Metrics: {KPIs and measurable outcomes}
98	- User Impact: {How users will benefit}
99
100	## Epic Acceptance Criteria
101
102	- [ ] {High-level requirement 1}
103	- [ ] {High-level requirement 2}
104	- [ ] {High-level requirement 3}
105
106	## Features in this Epic
107
108	- [ ] #{feature-issue-number} - {Feature Name}
109
110	## Definition of Done
111
112	- [ ] All feature stories completed
113	- [ ] End-to-end testing passed
114	- [ ] Performance benchmarks met
115	- [ ] Documentation updated
116	- [ ] User acceptance testing completed
117
118	## Labels
119
120	`epic`, `{priority-level}`, `{value-tier}`
121
122	## Milestone
123
124	{Release version/date}
125
126	## Estimate
127
128	{Epic-level t-shirt size: XS, S, M, L, XL, XXL}
129	```
130
131	##### Feature Issue Template
132
133	```markdown
134	# Feature: {Feature Name}
135
136	## Feature Description
137
138	{Feature summary from PRD}
139
140	## User Stories in this Feature
141
142	- [ ] #{story-issue-number} - {User Story Title}
143	- [ ] #{story-issue-number} - {User Story Title}
144
145	## Technical Enablers
146
147	- [ ] #{enabler-issue-number} - {Enabler Title}
148	- [ ] #{enabler-issue-number} - {Enabler Title}
149
150	## Dependencies
151
152	Blocks: {List of issues this feature blocks}
153	Blocked by: {List of issues blocking this feature}
154
155	## Acceptance Criteria
156
157	- [ ] {Feature-level re

People who liked this also viewed

6 picks

Type

breakdown-plan

9.1kinstalls4.6kforks

View on GitHub

How to install breakdown-plan?

github/awesome-copilot/breakdown-plan

$npx -y skills add github/awesome-copilot --skill breakdown-plan

Installs into the current project.

Summary

Issue Planning and Automation prompt that generates comprehensive project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated tracking.

Files · 1

View on GitHub

SKILL.md

1	# GitHub Issue Planning & Project Automation Prompt
2
3	## Goal
4
5	Act as a senior Project Manager and DevOps specialist with expertise in Agile methodology and GitHub project management. Your task is to take the complete set of feature artifacts (PRD, UX design, technical breakdown, testing plan) and generate a comprehensive GitHub project plan with automated issue creation, dependency linking, priority assignment, and Kanban-style tracking.
6
7	## GitHub Project Management Best Practices
8
9	### Agile Work Item Hierarchy
10
11	- Epic: Large business capability spanning multiple features (milestone level)
12	- Feature: Deliverable user-facing functionality within an epic
13	- Story: User-focused requirement that delivers value independently
14	- Enabler: Technical infrastructure or architectural work supporting stories
15	- Test: Quality assurance work for validating stories and enablers
16	- Task: Implementation-level work breakdown for stories/enablers
17
18	### Project Management Principles
19
20	- INVEST Criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
21	- Definition of Ready: Clear acceptance criteria before work begins
22	- Definition of Done: Quality gates and completion criteria
23	- Dependency Management: Clear blocking relationships and critical path identification
24	- Value-Based Prioritization: Business value vs. effort matrix for decision making
25
26	## Input Requirements
27
28	Before using this prompt, ensure you have the complete testing workflow artifacts:
29
30	### Core Feature Documents
31
32	1. Feature PRD: `/docs/ways-of-work/plan/{epic-name}/{feature-name}.md`
33	2. Technical Breakdown: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md`
34	3. Implementation Plan: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md`
35
36	### Related Planning Prompts
37
38	- Test Planning: Use `plan-test` prompt for comprehensive test strategy, quality assurance planning, and test issue creation
39	- Architecture Planning: Use `plan-epic-arch` prompt for system architecture and technical design
40	- Feature Planning: Use `plan-feature-prd` prompt for detailed feature requirements and specifications
41
42	## Output Format
43
44	Create two primary deliverables:
45
46	1. Project Plan: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md`
47	2. Issue Creation Checklist: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.md`
48
49	### Project Plan Structure
50
51	#### 1. Project Overview
52
53	- Feature Summary: Brief description and business value
54	- Success Criteria: Measurable outcomes and KPIs
55	- Key Milestones: Breakdown of major deliverables without timelines
56	- Risk Assessment: Potential blockers and mitigation strategies
57
58	#### 2. Work Item Hierarchy
59
60	```mermaid
61	graph TD
62	A[Epic: {Epic Name}] --> B[Feature: {Feature Name}]
63	B --> C[Story 1: {User Story}]
64	B --> D[Story 2: {User Story}]
65	B --> E[Enabler 1: {Technical Work}]
66	B --> F[Enabler 2: {Infrastructure}]
67
68	C --> G[Task: Frontend Implementation]
69	C --> H[Task: API Integration]
70	C --> I[Test: E2E Scenarios]
71
72	D --> J[Task: Component Development]
73	D --> K[Task: State Management]
74	D --> L[Test: Unit Tests]
75
76	E --> M[Task: Database Schema]
77	E --> N[Task: Migration Scripts]
78
79	F --> O[Task: CI/CD Pipeline]
80	F --> P[Task: Monitoring Setup]
81	```
82
83	#### 3. GitHub Issues Breakdown
84
85	##### Epic Issue Template
86
87	```markdown
88	# Epic: {Epic Name}
89
90	## Epic Description
91
92	{Epic summary from PRD}
93
94	## Business Value
95
96	- Primary Goal: {Main business objective}
97	- Success Metrics: {KPIs and measurable outcomes}
98	- User Impact: {How users will benefit}
99
100	## Epic Acceptance Criteria
101
102	- [ ] {High-level requirement 1}
103	- [ ] {High-level requirement 2}
104	- [ ] {High-level requirement 3}
105
106	## Features in this Epic
107
108	- [ ] #{feature-issue-number} - {Feature Name}
109
110	## Definition of Done
111
112	- [ ] All feature stories completed
113	- [ ] End-to-end testing passed
114	- [ ] Performance benchmarks met
115	- [ ] Documentation updated
116	- [ ] User acceptance testing completed
117
118	## Labels
119
120	`epic`, `{priority-level}`, `{value-tier}`
121
122	## Milestone
123
124	{Release version/date}
125
126	## Estimate
127
128	{Epic-level t-shirt size: XS, S, M, L, XL, XXL}
129	```
130
131	##### Feature Issue Template
132
133	```markdown
134	# Feature: {Feature Name}
135
136	## Feature Description
137
138	{Feature summary from PRD}
139
140	## User Stories in this Feature
141
142	- [ ] #{story-issue-number} - {User Story Title}
143	- [ ] #{story-issue-number} - {User Story Title}
144
145	## Technical Enablers
146
147	- [ ] #{enabler-issue-number} - {Enabler Title}
148	- [ ] #{enabler-issue-number} - {Enabler Title}
149
150	## Dependencies
151
152	Blocks: {List of issues this feature blocks}
153	Blocked by: {List of issues blocking this feature}
154
155	## Acceptance Criteria
156
157	- [ ] {Feature-level re

People who liked this also viewed

6 picks

Type