Back to Details

gsd-complete-milestone

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<objective> Mark milestone {{version}} complete, archive to milestones/, and update ROADMAP.md and REQUIREMENTS.md.
Purpose: Create historical record of shipped version, archive milestone artifacts (roadmap + requirements), and prepare for next milestone. Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tagged. </objective>
<execution_context> Load these files NOW (before proceeding):
  • @{{PLATFORM_ROOT}}/get-shit-done/workflows/complete-milestone.md (main workflow)
  • @{{PLATFORM_ROOT}}/get-shit-done/templates/milestone-archive.md (archive template) </execution_context>
<context> **Project files:** - `.planning/ROADMAP.md` - `.planning/REQUIREMENTS.md` - `.planning/STATE.md` - `.planning/PROJECT.md`
User input:
  • Version: {{version}} (e.g., "1.0", "1.1", "2.0") </context>
<process>
Follow complete-milestone.md workflow:
  1. Check for audit:
    • Look for 
      .planning/v{{version}}-MILESTONE-AUDIT.md
    • If missing or stale: recommend 
      {{COMMAND_PREFIX}}audit-milestone
      first
    • If audit status is 
      gaps_found
      : recommend 
      {{COMMAND_PREFIX}}plan-milestone-gaps
      first
    • If audit status is 
      passed
      : proceed to step 1
    markdown
    ## Pre-flight Check

{If no v{{version}}-MILESTONE-AUDIT.md:}
⚠ No milestone audit found. Run `{{COMMAND_PREFIX}}audit-milestone` first to verify
requirements coverage, cross-phase integration, and E2E flows.

{If audit has gaps:}
⚠ Milestone audit found gaps. Run `{{COMMAND_PREFIX}}plan-milestone-gaps` to create
phases that close the gaps, or proceed anyway to accept as tech debt.

{If audit passed:}
✓ Milestone audit passed. Proceeding with completion.
  2. Verify readiness:
    • Check all phases in milestone have completed plans (SUMMARY.md exists)
    • Present milestone scope and stats
    • Wait for confirmation
  3. Gather stats:
    • Count phases, plans, tasks
    • Calculate git range, file changes, LOC
    • Extract timeline from git log
    • Present summary, confirm
  4. Extract accomplishments:
    • Read all phase SUMMARY.md files in milestone range
    • Extract 4-6 key accomplishments
    • Present for approval
  5. Archive milestone:
    • Create 
      .planning/milestones/v{{version}}-ROADMAP.md
    • Extract full phase details from ROADMAP.md
    • Fill milestone-archive.md template
    • Update ROADMAP.md to one-line summary with link
  6. Archive requirements:
    • Create 
      .planning/milestones/v{{version}}-REQUIREMENTS.md
    • Mark all v1 requirements as complete (checkboxes checked)
    • Note requirement outcomes (validated, adjusted, dropped)
    • Delete 
      .planning/REQUIREMENTS.md
      (fresh one created for next milestone)
  7. Update PROJECT.md:
    • Add "Current State" section with shipped version
    • Add "Next Milestone Goals" section
    • Archive previous content in 
      <details>
      (if v1.1+)
  8. Commit and tag:
    • Stage: MILESTONES.md, PROJECT.md, ROADMAP.md, STATE.md, archive files
    • Commit: 
      chore: archive v{{version}} milestone
    • Tag: 
      git tag -a v{{version}} -m "[milestone summary]"
    • Ask about pushing tag
  9. Offer next steps:
    • {{COMMAND_PREFIX}}new-milestone
      — start next milestone (questioning → research → requirements → roadmap)
</process>
<success_criteria>
  • Milestone archived to 
    .planning/milestones/v{{version}}-ROADMAP.md
  • Requirements archived to 
    .planning/milestones/v{{version}}-REQUIREMENTS.md
  • .planning/REQUIREMENTS.md
    deleted (fresh for next milestone)
  • ROADMAP.md collapsed to one-line entry
  • PROJECT.md updated with current state
  • Git tag v{{version}} created
  • Commit successful
  • User knows next steps (including need for fresh requirements) </success_criteria>
<critical_rules>
  • Load workflow first: Read complete-milestone.md before executing
  • Verify completion: All phases must have SUMMARY.md files
  • User confirmation: Wait for approval at verification gates
  • Archive before deleting: Always create archive files before updating/deleting originals
  • One-line summary: Collapsed milestone in ROADMAP.md should be single line with link
  • Context efficiency: Archive keeps ROADMAP.md and REQUIREMENTS.md constant size per milestone
  • Fresh requirements: Next milestone starts with 
    {{COMMAND_PREFIX}}new-milestone
    which includes requirements definition </critical_rules>
<objective> 标记里程碑{{version}}为已完成，归档至milestones/，并更新ROADMAP.md和REQUIREMENTS.md。
目的：创建已发布版本的历史记录，归档里程碑相关文件（路线图+需求），并为下一个里程碑做准备。 输出：里程碑已归档（路线图+需求），PROJECT.md已更新，已创建Git标签。 </objective>
<execution_context> 立即加载以下文件（在执行前）：
  • @{{PLATFORM_ROOT}}/get-shit-done/workflows/complete-milestone.md（主工作流）
  • @{{PLATFORM_ROOT}}/get-shit-done/templates/milestone-archive.md（归档模板） </execution_context>
<context> **项目文件：** - `.planning/ROADMAP.md` - `.planning/REQUIREMENTS.md` - `.planning/STATE.md` - `.planning/PROJECT.md`
用户输入：
  • 版本：{{version}}（例如："1.0"、"1.1"、"2.0"） </context>
<process>
遵循complete-milestone.md工作流：
  1. 检查审计情况：
    • 查找
      .planning/v{{version}}-MILESTONE-AUDIT.md
      文件
    • 如果文件缺失或已过期：建议先执行
      {{COMMAND_PREFIX}}audit-milestone
    • 如果审计状态为
      gaps_found
      ：建议先执行
      {{COMMAND_PREFIX}}plan-milestone-gaps
    • 如果审计状态为
      passed
      ：继续执行步骤1
    markdown
    ## Pre-flight Check

{If no v{{version}}-MILESTONE-AUDIT.md:}
⚠ No milestone audit found. Run `{{COMMAND_PREFIX}}audit-milestone` first to verify
requirements coverage, cross-phase integration, and E2E flows.

{If audit has gaps:}
⚠ Milestone audit found gaps. Run `{{COMMAND_PREFIX}}plan-milestone-gaps` to create
phases that close the gaps, or proceed anyway to accept as tech debt.

{If audit passed:}
✓ Milestone audit passed. Proceeding with completion.
  2. 验证就绪状态：
    • 检查里程碑中的所有阶段是否都有已完成的计划（存在SUMMARY.md文件）
    • 展示里程碑范围和统计数据
    • 等待确认
  3. 收集统计数据：
    • 统计阶段、计划、任务的数量
    • 计算Git范围、文件变更数、代码行数（LOC）
    • 从Git日志中提取时间线
    • 展示汇总信息，等待确认
  4. 提取成果：
    • 读取里程碑范围内所有阶段的SUMMARY.md文件
    • 提取4-6项关键成果
    • 展示成果以获得批准
  5. 归档里程碑：
    • 创建
      .planning/milestones/v{{version}}-ROADMAP.md
    • 从ROADMAP.md中提取完整的阶段详情
    • 填充milestone-archive.md模板
    • 将ROADMAP.md更新为带链接的单行摘要
  6. 归档需求：
    • 创建
      .planning/milestones/v{{version}}-REQUIREMENTS.md
    • 将所有v1需求标记为已完成（勾选复选框）
    • 记录需求结果（已验证、已调整、已弃用）
    • 删除
      .planning/REQUIREMENTS.md
      （为下一个里程碑创建新文件）
  7. 更新PROJECT.md：
    • 添加包含已发布版本的"当前状态"章节
    • 添加"下一里程碑目标"章节
    • 将之前的内容归档到
      <details>
      标签中（如果是v1.1及以上版本）
  8. 提交并打标签：
    • 暂存文件：MILESTONES.md、PROJECT.md、ROADMAP.md、STATE.md以及归档文件
    • 提交：
      chore: archive v{{version}} milestone
    • 打标签：
      git tag -a v{{version}} -m "[milestone summary]"
    • 询问是否推送标签
  9. 提供后续步骤：
    • {{COMMAND_PREFIX}}new-milestone
      — 启动下一个里程碑（问题调研→研究→需求定义→路线图制定）
</process>
<success_criteria>
  • 里程碑已归档至
    .planning/milestones/v{{version}}-ROADMAP.md
  • 需求已归档至
    .planning/milestones/v{{version}}-REQUIREMENTS.md
  • .planning/REQUIREMENTS.md
    已删除（为下一个里程碑准备新文件）
  • ROADMAP.md已精简为单行条目
  • PROJECT.md已更新当前状态
  • 已创建Git标签v{{version}}
  • 提交成功
  • 用户了解后续步骤（包括需要创建新需求） </success_criteria>
<critical_rules>
  • **先加载工作流：**执行前先阅读complete-milestone.md
  • **验证完成状态：**所有阶段必须有SUMMARY.md文件
  • **用户确认：**在验证节点等待用户批准
  • **先归档再删除：**更新/删除原文件前必须先创建归档文件
  • **单行摘要：**ROADMAP.md中已归档的里程碑应为带链接的单行内容
  • **上下文效率：**归档可保持ROADMAP.md和REQUIREMENTS.md每个里程碑的文件大小稳定
  • **新需求准备：**下一个里程碑从
    {{COMMAND_PREFIX}}new-milestone
    开始，其中包含需求定义环节 </critical_rules>