Back to Details

roadmap-milestone

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
You are helping the user refine a single roadmap milestone.
你正在协助用户优化单个路线图里程碑。

Prerequisites

前置条件

The 
.spec-driven/
directory must exist at the project root. Before proceeding, verify:
ls .spec-driven/
If this fails, the project is not initialized. Run 
/spec-driven-init
first.
If 
.spec-driven/roadmap/
is missing, repair the scaffold first:
node {{SKILL_DIR}}/scripts/spec-driven.js init
.spec-driven/
目录必须存在于项目根目录下。继续操作前，请先验证：
ls .spec-driven/
如果该命令执行失败，说明项目尚未初始化，请先运行 
/spec-driven-init
。
如果缺少 
.spec-driven/roadmap/
目录，请先修复脚手架：
node {{SKILL_DIR}}/scripts/spec-driven.js init

Steps

操作步骤

  1. Choose the milestone — determine whether the user wants to edit an existing milestone or create a new one under 
    .spec-driven/roadmap/milestones/
    .
  2. Load milestone context — read:
    • .spec-driven/config.yaml
    • .spec-driven/roadmap/INDEX.md
    • the target milestone file when it already exists
    • any nearby milestone files needed to preserve ordering or avoid overlap
    • active and archived changes that the milestone already references or might need to reference
  3. Refine only one milestone at a time — help the user settle:
    • the milestone 
      Goal
    • Done Criteria
    • Candidate Ideas
    • Planned Changes
    • Dependencies / Risks
    • derived 
      Status
      Use these standard section headings in the file:
    • ## Goal
    • ## Done Criteria
    • ## Candidate Ideas
    • ## Planned Changes
    • ## Dependencies / Risks
    • ## Status
  4. Write the milestone file — create or update the milestone markdown file and keep it focused on that milestone only.
  5. Update roadmap index if needed — if the milestone is new, add it to 
    .spec-driven/roadmap/INDEX.md
    in the correct sequence.
  6. Enforce milestone status rules — if listed planned changes are not all archived, the milestone is not complete. Do not add manual completion overrides.
  7. Validate roadmap size before finish — run:
    node {{SKILL_DIR}}/scripts/spec-driven.js verify-roadmap
    If validation reports that the milestone is too large, stop and tell the user to split it instead of presenting the milestone as ready.
  8. Report the result — summarize what changed in the milestone and identify any candidate ideas that still need promotion into concrete changes.
  1. 选择里程碑 — 确定用户是想要编辑现有里程碑，还是在 
    .spec-driven/roadmap/milestones/
    目录下创建新的里程碑。
  2. 加载里程碑上下文 — 读取以下内容：
    • .spec-driven/config.yaml
    • .spec-driven/roadmap/INDEX.md
    • 目标里程碑文件（如果已存在）
    • 所有需要用于保持排序或避免内容重叠的相邻里程碑文件
    • 里程碑已引用或可能需要引用的活跃和已归档变更
  3. 每次仅优化一个里程碑 — 协助用户确定以下内容：
    • 里程碑 
      Goal
    • Done Criteria
    • Candidate Ideas
    • Planned Changes
    • Dependencies / Risks
    • 派生的 
      Status
      请在文件中使用以下标准章节标题：
    • ## Goal
    • ## Done Criteria
    • ## Candidate Ideas
    • ## Planned Changes
    • ## Dependencies / Risks
    • ## Status
  4. 编写里程碑文件 — 创建或更新里程碑Markdown文件，确保内容仅聚焦于当前里程碑。
  5. 按需更新路线图索引 — 如果是新建的里程碑，请将其按照正确的顺序添加到 
    .spec-driven/roadmap/INDEX.md
    中。
  6. 执行里程碑状态规则 — 如果列出的计划变更未全部归档，则里程碑未完成，请勿添加手动完成的覆盖配置。
  7. 完成前验证路线图规模 — 运行：
    node {{SKILL_DIR}}/scripts/spec-driven.js verify-roadmap
    如果验证结果显示里程碑规模过大，请停止操作并告知用户需要拆分里程碑，不要将其标记为就绪状态。
  8. 结果上报 — 总结里程碑中发生的变更，同时明确所有仍需升级为具体变更的候选创意。

Rules

规则

  • This is a planning/documentation skill only — do not change product code
  • Keep candidate ideas separate from planned changes
  • Keep milestone scope bounded; do not turn this into a whole-roadmap rewrite
  • Milestone completion is derived from archive state, not user preference
  • 这仅属于规划/文档相关的操作 — 请勿修改产品代码
  • 请将候选创意与计划变更分开
  • 保持里程碑范围边界清晰；不要将本次操作变成整个路线图的重写
  • 里程碑完成状态由归档状态派生得出，而非用户偏好决定