breakdown-plan by github/awesome-copilot
npx skills add https://github.com/github/awesome-copilot --skill breakdown-plan作为一名精通敏捷方法论和 GitHub 项目管理的高级项目经理和 DevOps 专家。你的任务是接收完整的特性工件集(PRD、UX 设计、技术分解、测试计划),并生成一个全面的 GitHub 项目计划,包括自动化 Issue 创建、依赖关系链接、优先级分配和看板式跟踪。
在使用此提示之前,请确保你拥有完整的测试工作流工件:
/docs/ways-of-work/plan/{epic-name}/{feature-name}.md广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
/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 提示进行全面的测试策略、质量保证规划和测试 Issue 创建plan-epic-arch 提示进行系统架构和技术设计plan-feature-prd 提示进行详细的特性需求和规范制定创建两个主要交付物:
/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md/docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.mdgraph TD
A[Epic: {Epic Name}] --> B[Feature: {Feature Name}]
B --> C[Story 1: {User Story}]
B --> D[Story 2: {User Story}]
B --> E[Enabler 1: {Technical Work}]
B --> F[Enabler 2: {Infrastructure}]
C --> G[Task: Frontend Implementation]
C --> H[Task: API Integration]
C --> I[Test: E2E Scenarios]
D --> J[Task: Component Development]
D --> K[Task: State Management]
D --> L[Test: Unit Tests]
E --> M[Task: Database Schema]
E --> N[Task: Migration Scripts]
F --> O[Task: CI/CD Pipeline]
F --> P[Task: Monitoring Setup]
# Epic: {Epic Name}
## Epic 描述
{Epic summary from PRD}
## 业务价值
- **主要目标**: {Main business objective}
- **成功指标**: {KPIs and measurable outcomes}
- **用户影响**: {How users will benefit}
## Epic 验收标准
- [ ] {High-level requirement 1}
- [ ] {High-level requirement 2}
- [ ] {High-level requirement 3}
## 本 Epic 中的特性
- [ ] #{feature-issue-number} - {Feature Name}
## 完成定义
- [ ] 所有特性 Story 已完成
- [ ] 端到端测试通过
- [ ] 性能基准测试达标
- [ ] 文档已更新
- [ ] 用户验收测试完成
## 标签
`epic`, `{priority-level}`, `{value-tier}`
## 里程碑
{Release version/date}
## 估算
{Epic-level t-shirt size: XS, S, M, L, XL, XXL}
# Feature: {Feature Name}
## 特性描述
{Feature summary from PRD}
## 本特性中的用户故事
- [ ] #{story-issue-number} - {User Story Title}
- [ ] #{story-issue-number} - {User Story Title}
## 技术使能项
- [ ] #{enabler-issue-number} - {Enabler Title}
- [ ] #{enabler-issue-number} - {Enabler Title}
## 依赖关系
**阻塞**: {List of issues this feature blocks}
**被阻塞于**: {List of issues blocking this feature}
## 验收标准
- [ ] {Feature-level requirement 1}
- [ ] {Feature-level requirement 2}
## 完成定义
- [ ] 所有用户故事已交付
- [ ] 技术使能项已完成
- [ ] 集成测试通过
- [ ] UX 评审通过
- [ ] 性能测试完成
## 标签
`feature`, `{priority-level}`, `{value-tier}`, `{component-name}`
## Epic
#{epic-issue-number}
## 估算
{Story points or t-shirt size}
# User Story: {Story Title}
## 故事陈述
作为一个 **{user type}**,我想要 **{goal}**,以便 **{benefit}**。
## 验收标准
- [ ] {Specific testable requirement 1}
- [ ] {Specific testable requirement 2}
- [ ] {Specific testable requirement 3}
## 技术任务
- [ ] #{task-issue-number} - {Implementation task}
- [ ] #{task-issue-number} - {Integration task}
## 测试要求
- [ ] #{test-issue-number} - {Test implementation}
## 依赖关系
**被阻塞于**: {Dependencies that must be completed first}
## 完成定义
- [ ] 验收标准已满足
- [ ] 代码评审通过
- [ ] 单元测试已编写并通过
- [ ] 集成测试通过
- [ ] UX 设计已实现
- [ ] 可访问性要求已满足
## 标签
`user-story`, `{priority-level}`, `frontend/backend/fullstack`, `{component-name}`
## Feature
#{feature-issue-number}
## 估算
{Story points: 1, 2, 3, 5, 8}
# Technical Enabler: {Enabler Title}
## 使能项描述
{Technical work required to support user stories}
## 技术要求
- [ ] {Technical requirement 1}
- [ ] {Technical requirement 2}
## 实施任务
- [ ] #{task-issue-number} - {Implementation detail}
- [ ] #{task-issue-number} - {Infrastructure setup}
## 支持的 User Stories
此使能项支持:
- #{story-issue-number} - {Story title}
- #{story-issue-number} - {Story title}
## 验收标准
- [ ] {Technical validation 1}
- [ ] {Technical validation 2}
- [ ] 性能基准测试达标
## 完成定义
- [ ] 实施完成
- [ ] 单元测试已编写
- [ ] 集成测试通过
- [ ] 文档已更新
- [ ] 代码评审通过
## 标签
`enabler`, `{priority-level}`, `infrastructure/api/database`, `{component-name}`
## Feature
#{feature-issue-number}
## 估算
{Story points or effort estimate}
| 优先级 | 价值 | 标准 | 标签 |
|---|---|---|---|
| P0 | 高 | 关键路径,阻塞发布 | priority-critical, value-high |
| P1 | 高 | 核心功能,面向用户 | priority-high, value-high |
| P1 | 中 | 核心功能,内部使用 | priority-high, value-medium |
| P2 | 中 | 重要但不阻塞 | priority-medium, value-medium |
| P3 | 低 | 锦上添花,技术债务 | priority-low, value-low |
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
## 冲刺 {N} 目标
**主要目标**: {本冲刺的主要交付物}
**冲刺中的故事**:
- #{issue} - {Story title} ({points} pts)
- #{issue} - {Story title} ({points} pts)
**总承诺量**: {points} 故事点
**成功标准**: {可衡量的结果}
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
epic、优先级、价值和团队标签/docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.md这种全面的 GitHub 项目管理方法确保了从 Epic 级别规划到单个实施任务的完全可追溯性,并具有自动化跟踪和所有团队成员的明确责任。
每周安装量
7.4K
仓库
GitHub Stars
26.7K
首次出现
Feb 25, 2026
安全审计
安装于
codex7.4K
gemini-cli7.3K
opencode7.3K
github-copilot7.3K
cursor7.3K
kimi-cli7.3K
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.mdgraph TD
A[Epic: {Epic Name}] --> B[Feature: {Feature Name}]
B --> C[Story 1: {User Story}]
B --> D[Story 2: {User Story}]
B --> E[Enabler 1: {Technical Work}]
B --> F[Enabler 2: {Infrastructure}]
C --> G[Task: Frontend Implementation]
C --> H[Task: API Integration]
C --> I[Test: E2E Scenarios]
D --> J[Task: Component Development]
D --> K[Task: State Management]
D --> L[Test: Unit Tests]
E --> M[Task: Database Schema]
E --> N[Task: Migration Scripts]
F --> O[Task: CI/CD Pipeline]
F --> P[Task: Monitoring Setup]
# 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}
| 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 |
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
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.
Weekly Installs
7.4K
Repository
GitHub Stars
26.7K
First Seen
Feb 25, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
codex7.4K
gemini-cli7.3K
opencode7.3K
github-copilot7.3K
cursor7.3K
kimi-cli7.3K
97,600 周安装
| P2 | Medium | Important but not blocking | priority-medium, value-medium |
| P3 | Low | Nice to have, technical debt | priority-low, value-low |