breakdown-plan

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

GitHub Issue Planning & Project Automation Prompt

GitHub Issue 规划与项目自动化提示词

Goal

目标

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.

担任具备敏捷方法论和GitHub项目管理专业知识的资深项目经理与DevOps专家。你的任务是利用完整的功能工件（PRD、UX设计、技术分解、测试计划），生成包含自动化问题创建、依赖关联、优先级分配和看板式跟踪的全面GitHub项目计划。

GitHub Project Management Best Practices

GitHub项目管理最佳实践

Agile Work Item Hierarchy

敏捷工作项层级

Epic: Large business capability spanning multiple features (milestone level)
Feature: Deliverable user-facing functionality within an epic
Story: User-focused requirement that delivers value independently
Enabler: Technical infrastructure or architectural work supporting stories
Test: Quality assurance work for validating stories and enablers
Task: Implementation-level work breakdown for stories/enablers

Epic：涵盖多个功能的大型业务能力（里程碑级别）
Feature：Epic下可交付的用户面向功能
Story：独立交付价值的用户聚焦需求
Enabler：支持Story的技术基础设施或架构工作
Test：验证Story和Enabler的质量保证工作
Task：Story/Enabler的实现级工作分解

Project Management Principles

项目管理原则

INVEST Criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
Definition of Ready: Clear acceptance criteria before work begins
Definition of Done: Quality gates and completion criteria
Dependency Management: Clear blocking relationships and critical path identification
Value-Based Prioritization: Business value vs. effort matrix for decision making

INVEST准则：独立（Independent）、可协商（Negotiable）、有价值（Valuable）、可估算（Estimable）、小型（Small）、可测试（Testable）
就绪定义：工作开始前明确验收标准
完成定义：质量门和完成标准
依赖管理：清晰的阻塞关系和关键路径识别
基于价值的优先级排序：业务价值与工作量矩阵决策

Input Requirements

输入要求

Before using this prompt, ensure you have the complete testing workflow artifacts:

使用本提示词前，请确保拥有完整的测试工作流工件：

Core Feature Documents

核心功能文档

Feature PRD:

/docs/ways-of-work/plan/{epic-name}/{feature-name}.md

Technical Breakdown:

/docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md

Implementation Plan:

/docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md

Feature PRD：

/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.md

Related Planning Prompts

Output Format

输出格式

Create two primary deliverables:

Project Plan:

/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md

Issue Creation Checklist:

/docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.md

创建两个主要交付物：

项目计划：

/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md

问题创建检查清单：

/docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.md

Project Plan Structure

项目计划结构

1. Project Overview

1. 项目概述

Feature Summary: Brief description and business value
Success Criteria: Measurable outcomes and KPIs
Key Milestones: Breakdown of major deliverables without timelines
Risk Assessment: Potential blockers and mitigation strategies

功能摘要：简要描述和业务价值
成功标准：可衡量的成果和KPI
关键里程碑：主要交付物分解（无时间线）
风险评估：潜在阻塞因素和缓解策略

2. Work Item Hierarchy

2. 工作项层级

mermaid

graph 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]

mermaid

graph 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]

3. GitHub Issues Breakdown

3. GitHub问题分解

Epic Issue Template

Epic问题模板

markdown

undefined

markdown

undefined

Epic: {Epic Name}

Epic Description

Epic描述

{Epic summary from PRD}

{来自PRD的Epic摘要}

Business Value

业务价值

Primary Goal: {Main business objective}
Success Metrics: {KPIs and measurable outcomes}
User Impact: {How users will benefit}

主要目标：{核心业务目标}
成功指标：{KPI和可衡量成果}
用户影响：{用户将如何受益}

Epic Acceptance Criteria

Epic验收标准

Features in this Epic

本Epic包含的功能

#{feature-issue-number} - {Feature Name}

#{feature-issue-number} - {Feature Name}

Definition of Done

完成定义

Labels

Milestone

里程碑

{Release version/date}

{发布版本/日期}

Estimate

估算

{Epic-level t-shirt size: XS, S, M, L, XL, XXL}

undefined

{Epic级T恤尺码: XS, S, M, L, XL, XXL}

undefined

Feature Issue Template

Feature问题模板

markdown

undefined

markdown

undefined

Feature: {Feature Name}

Feature Description

Feature描述

{Feature summary from PRD}

{来自PRD的Feature摘要}

User Stories in this Feature

本Feature包含的用户Story

#{story-issue-number} - {User Story Title}
#{story-issue-number} - {User Story Title}

#{story-issue-number} - {User Story标题}
#{story-issue-number} - {User Story标题}

Technical Enablers

技术Enabler

#{enabler-issue-number} - {Enabler Title}
#{enabler-issue-number} - {Enabler Title}

#{enabler-issue-number} - {Enabler标题}
#{enabler-issue-number} - {Enabler标题}

Dependencies

依赖关系

Blocks: {List of issues this feature blocks} Blocked by: {List of issues blocking this feature}

阻塞：{本Feature阻塞的问题列表} 被阻塞：{阻塞本Feature的问题列表}

Acceptance Criteria

验收标准

{Feature-level requirement 1}
{Feature-level requirement 2}

{Feature级需求1}
{Feature级需求2}

Definition of Done

完成定义

Labels

Epic

所属Epic

#{epic-issue-number}

Estimate

估算

{Story points or t-shirt size}

undefined

{Story点数或T恤尺码}

undefined

User Story Issue Template

用户Story问题模板

markdown

undefined

markdown

undefined

User Story: {Story Title}

User Story: {Story标题}

Story Statement

Story陈述

As a {user type}, I want {goal} so that {benefit}.

作为**{用户类型}，我希望{目标}，以便{收益}**。

Acceptance Criteria

验收标准

{Specific testable requirement 1}
{Specific testable requirement 2}
{Specific testable requirement 3}

{具体可测试需求1}
{具体可测试需求2}
{具体可测试需求3}

Technical Tasks

技术任务

#{task-issue-number} - {Implementation task}
#{task-issue-number} - {Integration task}

#{task-issue-number} - {实施任务}
#{task-issue-number} - {集成任务}

Testing Requirements

测试需求

#{test-issue-number} - {Test implementation}

#{test-issue-number} - {测试实施}

Dependencies

依赖关系

Blocked by: {Dependencies that must be completed first}

被阻塞：{必须先完成的依赖项}

Definition of Done

完成定义

Labels

Feature

所属Feature

#{feature-issue-number}

Estimate

估算

{Story points: 1, 2, 3, 5, 8}

undefined

{Story点数: 1, 2, 3, 5, 8}

undefined

Technical Enabler Issue Template

技术Enabler问题模板

markdown

undefined

markdown

undefined

Technical Enabler: {Enabler Title}

Technical Enabler: {Enabler标题}

Enabler Description

Enabler描述

{Technical work required to support user stories}

{支持用户Story所需的技术工作}

Technical Requirements

技术需求

{Technical requirement 1}
{Technical requirement 2}

{技术需求1}
{技术需求2}

Implementation Tasks

实施任务

#{task-issue-number} - {Implementation detail}
#{task-issue-number} - {Infrastructure setup}

#{task-issue-number} - {实施细节}
#{task-issue-number} - {基础设施搭建}

User Stories Enabled

支持的用户Story

This enabler supports:

#{story-issue-number} - {Story title}
#{story-issue-number} - {Story title}

本Enabler支持：

#{story-issue-number} - {Story标题}
#{story-issue-number} - {Story标题}

Acceptance Criteria

验收标准

Definition of Done

完成定义

Labels

Feature

所属Feature

#{feature-issue-number}

Estimate

估算

{Story points or effort estimate}

undefined

{Story点数或工作量估算}

undefined

4. Priority and Value Matrix

4. 优先级与价值矩阵

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`

优先级	价值	判定标准	标签
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`

5. Estimation Guidelines

5. 估算指南

Story Point Scale (Fibonacci)

Story点数规模（斐波那契数列）

1 point: Simple change, <4 hours
2 points: Small feature, <1 day
3 points: Medium feature, 1-2 days
5 points: Large feature, 3-5 days
8 points: Complex feature, 1-2 weeks
13+ points: Epic-level work, needs breakdown

1点：简单变更，<4小时
2点：小型功能，<1天
3点：中型功能，1-2天
5点：大型功能，3-5天
8点：复杂功能，1-2周
13+点：Epic级工作，需拆分

T-Shirt Sizing (Epics/Features)

T恤尺码（Epic/Feature）

XS: 1-2 story points total
S: 3-8 story points total
M: 8-20 story points total
L: 20-40 story points total
XL: 40+ story points total (consider breaking down)

XS：总计1-2个Story点
S：总计3-8个Story点
M：总计8-20个Story点
L：总计20-40个Story点
XL：总计40+个Story点（考虑拆分）

6. Dependency Management

6. 依赖关系管理

mermaid

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

mermaid

graph LR
    A[Epic规划] --> B[Feature定义]
    B --> C[Enabler实施]
    C --> D[Story开发]
    D --> E[测试执行]
    E --> F[Feature交付]

    G[基础设施搭建] --> C
    H[API设计] --> D
    I[数据库Schema] --> C
    J[身份验证] --> D

Dependency Types

依赖类型

Blocks: Work that cannot proceed until this is complete
Related: Work that shares context but not blocking
Prerequisite: Required infrastructure or setup work
Parallel: Work that can proceed simultaneously

阻塞（Blocks）：此工作完成前其他工作无法推进
相关（Related）：共享上下文但不阻塞的工作
前置条件（Prerequisite）：必需的基础设施或准备工作
并行（Parallel）：可同时推进的工作

7. Sprint Planning Template

7. 迭代规划模板

Sprint Capacity Planning

迭代容量规划

Team Velocity: {Average story points per sprint}
Sprint Duration: {2-week sprints recommended}
Buffer Allocation: 20% for unexpected work and bug fixes
Focus Factor: 70-80% of total time on planned work

团队速度：{每迭代平均Story点数}
迭代时长：{推荐2周迭代}
缓冲分配：20%用于意外工作和Bug修复
专注系数：70-80%的时间用于计划内工作

Sprint Goal Definition

迭代目标定义

markdown

undefined

markdown

undefined

Sprint {N} Goal

第{N}迭代目标

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}

undefined

主要目标：{本迭代核心交付物}

迭代包含的Story：

#{issue} - {Story标题} ({points} 点)
#{issue} - {Story标题} ({points} 点)

总承诺：{points} 个Story点 成功标准：{可衡量成果}

undefined

8. GitHub Project Board Configuration

8. GitHub项目看板配置

Column Structure (Kanban)

列结构（看板）

Backlog: Prioritized and ready for planning
Sprint Ready: Detailed and estimated, ready for development
In Progress: Currently being worked on
In Review: Code review, testing, or stakeholder review
Testing: QA validation and acceptance testing
Done: Completed and accepted

待办事项（Backlog）：已排序，待规划
迭代就绪（Sprint Ready）：细节完善且已估算，待开发
进行中（In Progress）：当前正在处理
评审中（In Review）：代码评审、测试或 stakeholder评审
测试中（Testing）：QA验证和验收测试
已完成（Done）：已完成并验收

Custom Fields Configuration

自定义字段配置

Priority: P0, P1, P2, P3
Value: High, Medium, Low
Component: Frontend, Backend, Infrastructure, Testing
Estimate: Story points or t-shirt size
Sprint: Current sprint assignment
Assignee: Responsible team member
Epic: Parent epic reference

优先级：P0, P1, P2, P3
价值：高、中、低
组件：前端、后端、基础设施、测试
估算：Story点数或T恤尺码
迭代：当前分配的迭代
负责人：负责的团队成员
Epic：父Epic引用

9. Automation and GitHub Actions

9. 自动化与GitHub Actions

Automated Issue Creation

自动化问题创建

yaml

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
            });

yaml

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
            });

Automated Status Updates

自动化状态更新

yaml

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

yaml

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
        # 将相关问题移至“In Review”列

      - name: Move to Done
        if: github.event.action == 'closed' && github.event.pull_request.merged
        uses: actions/github-script@v7
        # 将相关问题移至“Done”列

Issue Creation Checklist

问题创建检查清单

Pre-Creation Preparation

创建前准备

Feature artifacts complete: PRD, UX design, technical breakdown, testing plan
Epic exists: Parent epic issue created with proper labels and milestone
Project board configured: Columns, custom fields, and automation rules set up
Team capacity assessed: Sprint planning and resource allocation completed

功能工件完整：PRD、UX设计、技术分解、测试计划
Epic已存在：已创建父Epic问题并添加正确标签和里程碑
项目看板已配置：列、自定义字段和自动化规则已设置
团队容量已评估：迭代规划和资源分配已完成

Epic Level Issues

Epic级问题

Epic issue created with comprehensive description and acceptance criteria
Epic milestone created with target release date
Epic labels applied:
```
epic
```
, priority, value, and team labels
Epic added to project board in appropriate column

已创建Epic问题，包含全面描述和验收标准
已创建Epic里程碑，包含目标发布日期
已应用Epic标签：
```
epic
```
、优先级、价值和团队标签
Epic已添加至项目看板的对应列中

Feature Level Issues

Feature级问题

Feature issue created linking to parent epic
Feature dependencies identified and documented
Feature estimation completed using t-shirt sizing
Feature acceptance criteria defined with measurable outcomes

已创建Feature问题，关联至父Epic
已识别Feature依赖关系并记录
已完成Feature估算，使用T恤尺码
已定义Feature验收标准，包含可衡量成果

Story/Enabler Level Issues documented in

/docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.md

Story/Enabler级问题（记录于

/docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.md

）

Success Metrics

成功指标

Project Management KPIs

项目管理KPI

Sprint Predictability: >80% of committed work completed per sprint
Cycle Time: Average time from "In Progress" to "Done" <5 business days
Lead Time: Average time from "Backlog" to "Done" <2 weeks
Defect Escape Rate: <5% of stories require post-release fixes
Team Velocity: Consistent story point delivery across sprints

迭代可预测性：每迭代完成的承诺工作占比>80%
周期时间：从“进行中”到“已完成”的平均时间<5个工作日
前置时间：从“待办事项”到“已完成”的平均时间<2周
缺陷逃逸率：<5%的Story需要发布后修复
团队速度：各迭代的Story点交付保持稳定

Process Efficiency Metrics

流程效率指标

Issue Creation Time: <1 hour to create full feature breakdown
Dependency Resolution: <24 hours to resolve blocking dependencies
Status Update Accuracy: >95% automated status transitions working correctly
Documentation Completeness: 100% of issues have required template fields
Cross-Team Collaboration: <2 business days for external dependency resolution

问题创建时间：<1小时即可完成完整功能分解
依赖解决时间：<24小时解决阻塞依赖
状态更新准确率：>95%的自动化状态转换正常工作
文档完整性：100%的问题包含所需模板字段
跨团队协作效率：<2个工作日解决外部依赖

Project Delivery Metrics

项目交付指标

Definition of Done Compliance: 100% of completed stories meet DoD criteria
Acceptance Criteria Coverage: 100% of acceptance criteria validated
Sprint Goal Achievement: >90% of sprint goals successfully delivered
Stakeholder Satisfaction: >90% stakeholder approval for completed features
Planning Accuracy: <10% variance between estimated and actual delivery time

This 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.

完成定义合规性：100%已完成的Story符合DoD标准
验收标准覆盖率：100%的验收标准已验证
迭代目标达成率：>90%的迭代目标成功交付
Stakeholder满意度：已完成功能的Stakeholder批准率>90%
规划准确率：估算与实际交付时间的偏差<10%

这种全面的GitHub项目管理方法确保了从Epic级规划到单个实施任务的完整可追溯性，同时通过自动化跟踪明确了所有团队成员的职责。

breakdown-plan

Original

Translation

GitHub Issue Planning & Project Automation Prompt

GitHub Issue 规划与项目自动化提示词

Goal

目标

GitHub Project Management Best Practices

GitHub项目管理最佳实践

Agile Work Item Hierarchy

敏捷工作项层级

Project Management Principles

项目管理原则

Input Requirements

输入要求

Core Feature Documents

核心功能文档

Related Planning Prompts

相关规划提示词

Output Format

输出格式

Project Plan Structure

项目计划结构

1. Project Overview

1. 项目概述

2. Work Item Hierarchy

2. 工作项层级

3. GitHub Issues Breakdown

3. GitHub问题分解

Epic Issue Template

Epic问题模板

Epic: {Epic Name}

Epic: {Epic Name}

Epic Description

Epic描述

Business Value

业务价值

Epic Acceptance Criteria

Epic验收标准

Features in this Epic

本Epic包含的功能

Definition of Done

完成定义

Labels

标签

Milestone

里程碑

Estimate

估算

Feature Issue Template

Feature问题模板

Feature: {Feature Name}

Feature: {Feature Name}

Feature Description

Feature描述

User Stories in this Feature

本Feature包含的用户Story

Technical Enablers

技术Enabler

Dependencies

依赖关系

Acceptance Criteria

验收标准

Definition of Done

完成定义

Labels

标签

Epic

所属Epic

Estimate

估算

User Story Issue Template

用户Story问题模板

User Story: {Story Title}

User Story: {Story标题}

Story Statement

Story陈述

Acceptance Criteria

验收标准

Technical Tasks