npx skills add ...
npx skills add github/awesome-copilot --skill breakdown-plan
npx skills add github/awesome-copilot --skill breakdown-plan
Issue Planning and Automation prompt that generates comprehensive project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated tracking.
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.
Before using this prompt, ensure you have the complete testing workflow artifacts:
/docs/ways-of-work/plan/{epic-name}/{feature-name}.md/docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md/docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.mdplan-test prompt for comprehensive test strategy, quality assurance planning, and test issue creationplan-epic-arch prompt for system architecture and technical designplan-feature-prd prompt for detailed feature requirements and specificationsCreate two primary deliverables:
/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md/docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.md| Priority | Value | Criteria | Labels |
|---|---|---|---|
| P0 | High | Critical path, blocking release | priority-critical, value-high |
| P1 | High | Core functionality, user-facing | priority-high, value-high |
| P1 | Medium | Core functionality, internal | priority-high, value-medium |
| P2 | Medium | Important but not blocking | priority-medium, value-medium |
| P3 | Low | Nice to have, technical debt | priority-low, value-low |
epic, priority, value, and team labels/docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.mdThis comprehensive GitHub project management approach ensures complete traceability from epic-level planning down to individual implementation tasks, with automated tracking and clear accountability for all team members.
# Epic: {Epic Name}
## Epic Description
{Epic summary from PRD}
## Business Value
- **Primary Goal**: {Main business objective}
- **Success Metrics**: {KPIs and measurable outcomes}
- **User Impact**: {How users will benefit}
## Epic Acceptance Criteria
- [ ] {High-level requirement 1}
- [ ] {High-level requirement 2}
- [ ] {High-level requirement 3}
## Features in this Epic
- [ ] #{feature-issue-number} - {Feature Name}
## Definition of Done
- [ ] All feature stories completed
- [ ] End-to-end testing passed
- [ ] Performance benchmarks met
- [ ] Documentation updated
- [ ] User acceptance testing completed
## Labels
`epic`, `{priority-level}`, `{value-tier}`
## Milestone
{Release version/date}
## Estimate
{Epic-level t-shirt size: XS, S, M, L, XL, XXL}# Feature: {Feature Name}
## Feature Description
{Feature summary from PRD}
## User Stories in this Feature
- [ ] #{story-issue-number} - {User Story Title}
- [ ] #{story-issue-number} - {User Story Title}
## Technical Enablers
- [ ] #{enabler-issue-number} - {Enabler Title}
- [ ] #{enabler-issue-number} - {Enabler Title}
## Dependencies
**Blocks**: {List of issues this feature blocks}
**Blocked by**: {List of issues blocking this feature}
## Acceptance Criteria
- [ ] {Feature-level requirement 1}
- [ ] {Feature-level requirement 2}
## Definition of Done
- [ ] All user stories delivered
- [ ] Technical enablers completed
- [ ] Integration testing passed
- [ ] UX review approved
- [ ] Performance testing completed
## Labels
`feature`, `{priority-level}`, `{value-tier}`, `{component-name}`
## Epic
#{epic-issue-number}
## Estimate
{Story points or t-shirt size}# User Story: {Story Title}
## Story Statement
As a **{user type}**, I want **{goal}** so that **{benefit}**.
## Acceptance Criteria
- [ ] {Specific testable requirement 1}
- [ ] {Specific testable requirement 2}
- [ ] {Specific testable requirement 3}
## Technical Tasks
- [ ] #{task-issue-number} - {Implementation task}
- [ ] #{task-issue-number} - {Integration task}
## Testing Requirements
- [ ] #{test-issue-number} - {Test implementation}
## Dependencies
**Blocked by**: {Dependencies that must be completed first}
## Definition of Done
- [ ] Acceptance criteria met
- [ ] Code review approved
- [ ] Unit tests written and passing
- [ ] Integration tests passing
- [ ] UX design implemented
- [ ] Accessibility requirements met
## Labels
`user-story`, `{priority-level}`, `frontend/backend/fullstack`, `{component-name}`
## Feature
#{feature-issue-number}
## Estimate
{Story points: 1, 2, 3, 5, 8}# Technical Enabler: {Enabler Title}
## Enabler Description
{Technical work required to support user stories}
## Technical Requirements
- [ ] {Technical requirement 1}
- [ ] {Technical requirement 2}
## Implementation Tasks
- [ ] #{task-issue-number} - {Implementation detail}
- [ ] #{task-issue-number} - {Infrastructure setup}
## User Stories Enabled
This enabler supports:
- #{story-issue-number} - {Story title}
- #{story-issue-number} - {Story title}
## Acceptance Criteria
- [ ] {Technical validation 1}
- [ ] {Technical validation 2}
- [ ] Performance benchmarks met
## Definition of Done
- [ ] Implementation completed
- [ ] Unit tests written
- [ ] Integration tests passing
- [ ] Documentation updated
- [ ] Code review approved
## Labels
`enabler`, `{priority-level}`, `infrastructure/api/database`, `{component-name}`
## Feature
#{feature-issue-number}
## Estimate
{Story points or effort estimate}graph LR
A[Epic Planning] --> B[Feature Definition]
B --> C[Enabler Implementation]
C --> D[Story Development]
D --> E[Testing Execution]
E --> F[Feature Delivery]
G[Infrastructure Setup] --> C
H[API Design] --> D
I[Database Schema] --> C
J[Authentication] --> D## Sprint {N} Goal
**Primary Objective**: {Main deliverable for this sprint}
**Stories in Sprint**:
- #{issue} - {Story title} ({points} pts)
- #{issue} - {Story title} ({points} pts)
**Total Commitment**: {points} story points
**Success Criteria**: {Measurable outcomes}name: Create Feature Issues
on:
workflow_dispatch:
inputs:
feature_name:
description: 'Feature name'
required: true
epic_issue:
description: 'Epic issue number'
required: true
jobs:
create-issues:
runs-on: ubuntu-latest
steps:
- name: Create Feature Issue
uses: actions/github-script@v7
with:
script: |
const { data: epic } = await github.rest.issues.get({
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: ${{ github.event.inputs.epic_issue }}
});
const featureIssue = await github.rest.issues.create({
owner: context.repo.owner,
repo: context.repo.repo,
title: `Feature: ${{ github.event.inputs.feature_name }}`,
body: `# Feature: ${{ github.event.inputs.feature_name }}\n\n...`,
labels: ['feature', 'priority-medium'],
milestone: epic.data.milestone?.number
});name: Update Issue Status
on:
pull_request:
types: [opened, closed]
jobs:
update-status:
runs-on: ubuntu-latest
steps:
- name: Move to In Review
if: github.event.action == 'opened'
uses: actions/github-script@v7
# Move related issues to "In Review" column
- name: Move to Done
if: github.event.action == 'closed' && github.event.pull_request.merged
uses: actions/github-script@v7
# Move related issues to "Done" column