claude-skills 项目「retrospectives:complete-epic」命令全解验证票据、生成 12 节完成报告并闭环 Epic【免费下载链接】claude-skills67 Specialized Skills for Full-Stack Developers. Transform Claude Code into your expert pair programmer.项目地址: https://gitcode.com/GitHub_Trending/claud/claude-skillsretrospectives:complete-epic是 claude-skills 项目六阶段工作流intake → discovery → planning → execution → retrospectives中收尾闭环的核心命令它先验证 Epic 下所有票据已进入 Done 状态再生成一份覆盖交付物、架构决策、质量指标、技术债、经验教训与风险回顾的 12 节完成报告随后将 Confluence 文档归档到 Complete 目录、在 Jira 中关闭 Epic并对docs/system-description.md做整体性而非增量式的系统描述审查。读完本文你将掌握该命令的输入输出契约、五个执行阶段、全部强制检查点checkpoint、12 节报告模板与失败处理策略并能将其直接接入自己的 Claude Code 项目工作流。一、命令定位工作流闭环的最后一环retrospectives:complete-epic属于 retrospective回顾阶段其机器可读契约定义在 commands/project/retrospectives/complete-epic.yaml对应的人类可读流程文档为 docs/workflow/retrospective-complete-epic.md具体执行实现则位于 commands/project/retrospectives/complete-epic.md。根据 commands/workflow-manifest.yaml 中的阶段依赖关系retrospectives 阶段以depends_on: execution (required)严格依赖执行阶段位于整个工作流 DAG 的末端intake → discovery → planning → execution → retrospectives:complete-epic在 commands/project/retrospectives/complete-epic.md 的 Workflow Chain 一节中完整调用链被描述为/create-create-epic-plan epic-key → Creates Overview Document ↓ /create-implementation-plan overview-doc-url → Creates Implementation Plan ↓ /execute-ticket ticket-key → Executes individual tickets ↓ /complete-epic epic-key → Completes epic (YOU ARE HERE) ↓ /complete-sprint sprint-folder → Sprint retrospective从源码结构看complete-sprint命令文件仍存在于仓库中commands/project/retrospectives/complete-sprint.md但 docs/WORKFLOW_COMMANDS.md 第 626 行明确标注Sprint-level retrospectives (complete-sprint) have been removed in favor of epic-level analysis withretrospectives:complete-epic.——即当前版本已用 Epic 级回顾替代了 Sprint 级回顾复盘粒度被收敛到每个 Epic 上。命令的核心职责根据 docs/workflow/retrospective-phase.md 与命令实现complete-epic 一次调用需要完成四件相互独立的事验证收尾核对所有关联票据状态存在未完成票据时阻塞报告生成产出 12 节完整完成报告文档与票据归档Confluence 文档从 In Progress 移至 CompleteJira Epic 关闭整体系统描述审查对docs/system-description.md做全局性核对确保架构图、API 面、依赖图反映 Epic 完成后的真实状态。其中第四点尤其值得注意它不是对系统描述的增量追加而是holistic check——因为逐票据的增量更新可能遗漏跨票据的架构级变化只有在 Epic 全部收口时做一次整体审查才能捕获这些被遗漏的变更。二、命令契约输入、输出与前置条件命令的正式接口由 YAML 契约定义command: retrospectives:complete-epic phase: retrospective path: commands/project/retrospectives/complete-epic.md description: docs/workflow/retrospective-complete-epic.md inputs: - name: epic-key type: string required: true description: Jira epic key to complete (e.g., CC-62) outputs: - name: completion-report type: report description: Comprehensive epic completion report covering deliverables, quality metrics, lessons learned, and risk review - name: closed-epic type: tickets description: Epic closed in Jira with status Done and resolution Completed - name: updated-system-description type: file path: docs/system-description.md description: System description updated with holistic post-epic review of architecture, APIs, and dependencies requires: - ticketing - documentation status: existing argument-hint: epic-key repeat: false输入名称类型必填说明epic-keystringyes要收尾的 Jira Epic 键例如CC-62输出名称类型说明completion-reportreport12 节完成报告summary、objectives、tickets、deliverables、architecture、quality、debt、testing、docs、lessons、risks、recommendationsclosed-epictickets已在 Jira 中以 Done 状态和 Completed resolution 关闭的 Epicupdated-system-descriptionfile经整体性事后审查更新后的docs/system-description.md按 docs/workflow/workflow-definition-schema.md 的字段规范requires声明了该命令依赖ticketingJira与documentationConfluence两类后端能力argument-hint: epic-key给出了 CLI 调用形态——实际执行时形如/project:retrospectives:complete-epic epic-key见 docs/WORKFLOW_COMMANDS.md 第 593 行。前置条件Epic 内所有票据均已完成或在用户明确授权下移入 backlogOverview Document概览文档与 Implementation Plan实施计划可在 Confluence 中访问已正确配置 Jira 与 Confluence 访问权限。三、Phase 0上下文检索Context Retrieval命令的第一阶段是从 Jira 拉取 Epic 并建立上下文获取 Epic用{Epic_Key}从 Jira 拉取该 Epic抽取关键信息{Epic_Title}—— Epic 标题/名称{Jira_Project}—— Jira 项目 URL全部关联票据Epic 当前状态定位文档在 Confluence 的/Epics/In Progress/{Epic_Key}/下查找 Overview Document查找 Implementation PlanOverview Document 的子页面。失败条件文档缺失若无法定位文档必须立即停止并向用户呈现如下提示未确认前不得继续I was unable to locate the required documents for epic {Epic_Key}. Please provide: 1. Overview Document URL: [paste link] 2. Implementation Plan URL: [paste link]强制检查点Epic 收尾就绪性确认Please confirm the following before proceeding with epic completion: Epic: {Epic_Key} - {Epic_Title} Total Tickets: [count] Completed Tickets: [count] In Progress: [count] Blocked: [count] Overview Document: {Overview_Document} Implementation Plan: {Implementation_Plan} Are all tickets complete and ready to close this epic? (Yes / No / Review)Yes→ 进入 Phase 1No→ 列出未完成票据并退出Review→ 展示详细的票据状态明细。在没有用户明确 override 的情况下存在未完成票据时不得继续。这一检查点checkpoint加阻塞blocking设计贯穿命令全程是保证 Agent 不会在数据不完备时贸然行动的关键机制。四、Phase 1验证Verification1. 验证全部票据完成逐一检查 Epic 下每个票据在 Jira 中的状态找出所有非 Done 状态的票据检查是否存在阻塞问题或未解决的依赖。失败条件存在未完成票据Epic {Epic_Key} has incomplete tickets: In Progress: - [TICKET-KEY]: [Title] - Status: [status] Blocked: - [TICKET-KEY]: [Title] - Blocker: [reason] To Do: - [TICKET-KEY]: [Title] Options: A) Complete remaining tickets first B) Move incomplete tickets to backlog and close epic C) Extend epic deadline and keep open What would you like to do? [A/B/C]必须等待用户决策后才能继续。注意这里的 B 选项与 docs/workflow/retrospective-complete-epic.md 中前置条件的或经用户 override 明确移入 backlog遥相呼应——未完成票据只有在用户显式授权时才允许被移出作用域。2. 审查实现质量核对所有与 Epic 票据相关的 PR 均已合并验证测试覆盖率是否达到 90% 目标该阈值在报告与输出模板中被反复引用是项目的默认质量基准审查任何已记录的偏差或技术债。五、Phase 212 节 Epic 完成报告核心产物验证通过后命令生成一份覆盖以下 12 个章节的完整完成报告。这是整个命令最重要的交付物其内容骨架必须被完整保留1. Epic SummaryEpic 摘要Epic:{Epic_Key} - {Epic_Title}Duration:开始日期 → 完成日期Total Story Points:计划值 vs. 实际值Tickets Completed:[count]Team Members:贡献者列表2. Objectives Outcomes目标与成果Original Goals:取自 Overview DocumentSuccess Metrics:取自 Overview DocumentOutcomes Achieved:每个目标标注 Met / Partially Met / Not Met 并附说明Business Impact:可量化的结果受影响用户数、性能提升等3. Ticket Breakdown票据明细TicketTitlePointsCompletedDeviations[KEY][title][pts][date][any deviations]Summary:Total tickets: [count]Average cycle time: [days]Tickets with deviations: [count]Follow-up tickets created: [count]4. Technical Deliverables技术交付物Files Created:[count] files含主要组件列表Files Modified:[count] files含重要改动列表Lines of Code:[additions] / -[deletions]Test Coverage:Unit tests: [count] tests, [%] coverageIntegration tests: [count] testsE2E tests: [count] testsOverall coverage: [%]target: 90%5. Architecture Design Decisions架构与设计决策Key Architectural Patterns Used:每个模式附说明及受影响文件Design Tradeoffs:每个决策说明选择了什么 vs. 替代方案、以及理由Reusable Components Created:可复用于后续工作的组件清单6. Quality Metrics质量指标Code Review:PRs created / Average review time / Revision roundsBug Tracking:Bugs found during development / in production / Critical issuesPre-commit/Pre-push Hooks:Pass rate / Common failures7. Technical Debt Follow-up技术债与后续Technical Debt Incurred:每项说明原因与补救计划Follow-up Tickets Created:[TICKET-KEY]: [Title] - [Priority] - [Sprint placement]Refactoring Opportunities:未来可改进区域Performance Optimizations:可优化区域8. Testing Quality Assurance测试与质量保证Test Strategy Effectiveness:测试是否早期捕获问题、覆盖的边界用例、新增回归测试数量Quality Issues:测试遗漏的问题、后续测试改进建议9. Documentation Delivered交付的文档Confluence Pages:Overview Document、Implementation Plan 及其他新建文档Code Documentation:JSDoc coverage、README updates、API documentationRunbook Updates:新增的运维文档10. Lessons Learned经验教训What Went Well:成功项附详细描述与示例What Could Be Improved:挑战项附影响与规避方式Process Improvements:具体改进建议11. Risk Assessment Review风险回顾对比 Overview Document 中计划的风险与实际结果RiskPlanned LevelActual ImpactMitigation Effectiveness[Risk 1][Low/Med/High][description][Effective/Partial/Ineffective]Unexpected Risks Encountered:未预见的风险及处理方式12. Recommendations for Future Epics对后续 Epic 的建议Planning Phase / Implementation Phase / Testing Phase三个维度各列具体建议。这 12 节结构也与 docs/WORKFLOW_COMMANDS.md 第 606-618 行登记的报告章节清单完全一致是跨文档同步约定的契约可在生成报告时直接作为校验清单。六、Phase 3文档更新Documentation Updates报告生成后进入文档更新阶段但必须先过强制检查点## Proposed Documentation Updates ### 1. Overview Document Updates I will add the following Completion Report section to {Overview_Document}: [Show exact content to be added] ### 2. Move to Complete Folder I will move the epic documentation from: FROM: /Epics/In Progress/{Epic_Key}/ TO: /Epics/Complete/Sprint [N]/{Epic_Key}/ ### 3. Update All Ticket Links I will update all [count] tickets to point to the new location. Proceed with these updates? (Yes / No / Modify)未经明确批准不得更新任何文档。这一检查点的价值在于Agent 需要先展示将要写入的确切内容[Show exact content to be added]把写什么和写到哪里都暴露给用户审查防止自动 Agent 在文档归档过程中引入错误信息。七、Phase 4发布与关闭Publish Close发布完成报告作为新章节追加到 Overview Document可选地创建独立的 Completion Report 子页面归档文档从/Epics/In Progress/{Epic_Key}/移至/Epics/Complete/Sprint [N]/{Epic_Key}/并更新所有内部链接更新全部票据添加完成日期、更新文档链接指向新位置、添加完成报告链接强制检查点——关闭 EpicReady to close epic {Epic_Key} in Jira? This will: - Set epic status to Done - Update resolution to Completed - Add completion comment with report link Proceed? (Yes / No)未经明确批准不得关闭 Epic。在 Jira 中关闭 Epic设置状态为 Done、resolution 为 Completed、添加包含报告链接的评论生成 Sprint 文件夹引用确定该 Epic 所属 Sprint记录 Sprint 文件夹路径以供后续回顾使用。这里记录 Sprint 文件夹路径是为了衔接下一个潜在动作——虽然complete-sprint在当前版本已被移除见前文 docs/WORKFLOW_COMMANDS.md 的说明但实现文档仍保留了该交接位体现了工作流演进的历史脉络。八、Phase 5知识转移Knowledge TransferEpic 关闭不代表价值终止命令的最后阶段负责把经验沉淀回团队识别可复用模式记录应在后续工作中使用的新模式若建立了新的编码规范更新AGENTS.md若创建了新命令或工作流更新CLAUDE.md分享关键学习对团队其他成员有价值的技术洞见、应采纳的流程改进、被证明有效的工具或技巧更新团队文档架构决策记录ADR、设计模式库、最佳实践指南。命令实现文件的末尾还给出了Agent Delegation代理委派建议供 Agent 在执行不同子任务时委派给专门的分析维度Data Analysis系统性分析 git 历史、PR 数据与测试覆盖率Documentation Review审查完成报告的完整性与准确性Quality Assessment客观评估测试覆盖率、代码质量与技术债Knowledge Extraction从 Epic 执行中提取模式、经验与建议Process Analysis评估工作流效率并识别改进机会。九、失败条件一览与最终输出失败条件处理表条件处理方式Epic 未找到报错请用户核对 Epic key存在未完成票据报告未完成票据等待用户决策文档未找到询问用户文档位置无法移动 Confluence 页面请用户手动移动并给出操作指引无法在 Jira 关闭 Epic报告错误给出手动操作指引缺少 git 历史/PR 数据基于可用数据生成报告并注明缺口命令完成时的强制输出模板命令实现规定完成时必须输出如下结构化摘要## Epic Completion Successful! **Epic:** {Epic_Key} - {Epic_Title} ### Summary - Total Story Points: [planned] → [actual] - Total Tickets: [count] completed - Duration: [start date] → [end date] ([X] days) - Test Coverage: [%] (target: 90%) - Follow-up Tickets: [count] created ### Documentation - **Completion Report:** {Completion_Report_URL} - **Overview Document:** {Overview_Document} (updated) - **Implementation Plan:** {Implementation_Plan} - **New Location:** /Epics/Complete/Sprint [N]/{Epic_Key}/ ### Key Deliverables - [count] files created - [count] files modified - [count] unit tests added - [count] integration tests added - [count] E2E tests added ### Technical Debt - [count] items identified (see completion report) - [count] follow-up tickets created ### Lessons Learned (Top 3) 1. [Lesson 1] 2. [Lesson 2] 3. [Lesson 3] ### Next Steps - Review follow-up tickets: [list tickets with links] - Sprint folder ready for retrospective: /Epics/Complete/Sprint [N]/ - Run /complete-sprint [N] when sprint is completeCRITICALSprint 文件夹位置是进行 Sprint 回顾所必需的。该模板把完成结果压缩为一眼可读的摘要同时保留了对后续动作的指引。十、整体性系统描述审查比增量更新更进一步最后回到命令概览中强调的holistic system description review。这个动作的对象是docs/system-description.md——它由 intake 阶段的intake:create-system-description命令生成。根据 docs/workflow/intake-create-system-description.md 的说明该文档以并行分析线程产出覆盖架构服务、数据库、队列、API 表面、安全模式认证、加密、访问控制与外部依赖定位是适合审计者或新任资深工程师阅读的 SOC2 风格活文档并作为后续所有工作流阶段的共享上下文。The system description is complete. Feature-forge reads it during feature definition... This document becomes the shared context for all subsequent workflow phases, and is incrementally updated during execution and holistically reviewed during retrospective.这句描述点明了 complete-epic 中系统描述审查的价值所在执行阶段的逐票据更新是增量式的可能漏掉跨票据的架构级变化而 retrospective 阶段对docs/system-description.md的整体审查则确保架构图、API 表面、依赖映射全面反映 Epic 完成后的最终状态。二者互补构成了执行期增量 收尾期整体的双层文档保鲜机制。十一、工作流循环收尾即新起点命令的 Next Steps 语义构成了工作流的外循环The system description is now current. The nextfeature-forgeinvocation reads the updated system description, and the workflow cycle begins again. The sprint folder location is available forcomplete-sprintif a sprint retrospective is needed.同样地docs/workflow/retrospective-phase.md 也强调The updated system description feeds the next cycle. When the next feature is defined viafeature-forge, it reads the current system description, making each iteration more informed than the last.也就是说retrospectives:complete-epic不仅关闭了当前 Epic还通过更新系统描述为下一轮迭代提供更准确的全局上下文——每次循环都让 Agent 对系统现状的理解更进一步。配合 docs/workflow/execution-phase.md 中所有票据完成后进入 Retrospective Phase 关闭 Epic 并生成完成报告的衔接指引整个六阶段工作流由此形成定义 → 规划 → 执行 → 回顾 → 再定义的自增强闭环。如果你正尝试在自己的项目中复刻这套流程最直接的落地方式是把 commands/project/retrospectives/complete-epic.md 的五个阶段与全部检查点原样移植为命令提示词并按 commands/project/retrospectives/complete-epic.yaml 的契约声明输入输出再通过 docs/workflow/workflow-definition-schema.md 中定义的校验规则命令唯一性、路径可解析、阶段引用有效等纳入工作流清单 commands/workflow-manifest.yaml即可获得同样可靠的验证—报告—归档—关闭—复盘五步收尾能力。【免费下载链接】claude-skills67 Specialized Skills for Full-Stack Developers. Transform Claude Code into your expert pair programmer.项目地址: https://gitcode.com/GitHub_Trending/claud/claude-skills创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考