agile-roadmap

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Roadmap Planning

路线图规划

Use this skill to transform broad objectives into clear, prioritized roadmaps connected to the executable backlog.

Initial context received via slash: $ARGUMENTS

$ARGUMENTS

is filled, use as starting point (e.g., intake, initiative list, period). If empty, ask for the roadmap objective.

使用该技能将宽泛的目标转化为与可执行待办事项关联的清晰、优先级明确的路线图。

通过斜杠命令接收初始上下文：$ARGUMENTS

若

$ARGUMENTS

已填写，则将其作为起点（例如：需求收集、计划列表、周期）。若为空，则询问路线图目标。

Language

语言

Write the artifact in the user's language. Apply correct grammar and any required diacritics or script-specific characters. If the user's language is unclear, ask before generating output. Templates are in English — translate headers and content to match.

使用用户的语言编写产物。应用正确的语法以及所需的变音符号或特定脚本字符。若用户的语言不明确，在生成输出前先询问。模板为英文——需将标题和内容翻译为匹配的语言。

Project root

项目根目录

This skill writes artifacts at paths relative to the project root (the repo where the work happens), not the agent's current working directory.

If invoked from inside the project, use the relative paths shown in this skill.
If invoked from another directory (e.g., a sibling repo, or when the project lives elsewhere), prepend
```
<project-root>/
```
to every artifact path.
When the project root is ambiguous, confirm with the user via the harness question tool before writing.

该技能在相对于项目根目录（开展工作的仓库）的路径下编写产物，而非Agent的当前工作目录。

若从项目内部调用，使用本技能中显示的相对路径。
若从其他目录调用（例如：同级仓库，或项目位于其他位置），在每个产物路径前添加
```
<project-root>/
```
。
当项目根目录不明确时，在编写前通过harness问题工具与用户确认。

Prompting

提示方式

Follow the project-wide convention in

CLAUDE.md

AGENTS.md

("Skill Prompting Conventions"). Use the harness's structured-question tool —

AskUserQuestion

(Claude Code),

ask_user_question

(Codex), or

question

(OpenCode) — for the decision points below. Use free-form text only where a path/name/value cannot be enumerated.

Decision point	Why structured	Suggested options
Roadmap type	Affects template variant	Trajectory · Quarterly
Next initiative to decompose	Branches the next skill	first initiative · pick from list

Free-form prompts (no structured tool):

Period bounds (if quarterly)
Initiative descriptions

No-pause mode: if the user has explicitly disabled mid-skill clarification, convert every structured prompt into an entry under Open questions (or equivalent) and proceed without blocking.

遵循

CLAUDE.md

AGENTS.md

中的项目级约定（"技能提示约定"）。针对以下决策点，使用harness的结构化问题工具——

AskUserQuestion

（Claude Code）、

ask_user_question

（Codex）或

question

（OpenCode）。仅在路径/名称/值无法枚举时使用自由格式文本。

决策点	为何使用结构化方式	建议选项
路线图类型	影响模板变体	轨迹型 · 季度型
下一步要分解的计划	决定后续技能分支	首个计划 · 从列表中选择

自由格式提示（不使用结构化工具）：

周期范围（若为季度型）
计划描述

无暂停模式：若用户明确禁用技能执行中的澄清步骤，则将每个结构化提示转换为「待解决问题」（或等效项）下的条目，无需等待直接继续执行。

When to use

适用场景

Roadmap is defined by trajectory complexity, not by duration. Use this skill when 2+ apply:

Multiple initiatives/phases need sequencing (can't all run in parallel)
Decisions today affect future decisions (local optimization can become tech debt)
Stakeholders need to see the whole journey before approving individual steps
External dependencies (other teams, vendors, deadlines)
Total complexity exceeds what fits in a single epic

A 4-week initiative with 5 sequenced phases also benefits from a roadmap — don't dismiss it as "too short".

路线图由轨迹复杂度而非时长定义。当满足以下2个及以上条件时使用本技能：

多个计划/阶段需要排序（无法全部并行执行）
当前决策会影响未来决策（局部优化可能演变为技术债务）
利益相关者需要在批准单个步骤前了解完整流程
存在外部依赖（其他团队、供应商、截止日期）
总复杂度超出单个史诗（Epic）的覆盖范围

一个包含5个有序阶段的4周计划同样能从中获益——不要因其“时长太短”而忽视。

When NOT to use

不适用场景

Isolated, self-contained initiative (single epic covers it)
Single epic with no ramifications — go straight to
```
/agile-epic
```
Team already has the trajectory clear in mind and no stakeholder needs the map

孤立、独立的计划（单个史诗即可覆盖）
无后续影响的单个史诗——直接使用
```
/agile-epic
```
团队已清晰了解轨迹且利益相关者无需该路线图

Scope (types of roadmap)

范围（路线图类型）

Trajectory roadmap: multi-phase initiative with dependencies between phases (any duration)
Initiative roadmap: phases, stories, unblocks, and delivery order for a named initiative
Quarterly roadmap: direction alignment, period objectives, and macro priorities (one specific type — not the only one)

轨迹型路线图：阶段间存在依赖关系的多阶段计划（任意时长）
计划型路线图：指定计划的阶段、用户故事、障碍消除和交付顺序
季度型路线图：方向对齐、周期目标和宏观优先级（一种特定类型——并非唯一类型）

Operating rules

操作规则

Roadmap must focus on results and capabilities, not extensive technical lists.
Every roadmap item must indicate expected value, dependencies, and progress signal.
The roadmap must show what is a commitment, what is a risk, and what is outside the period.
Whenever possible, each initiative should point to a corresponding epic.

路线图必须聚焦于成果和能力，而非冗长的技术列表。
每个路线图条目必须标明预期价值、依赖关系和进度信号。
路线图必须明确显示哪些是承诺事项、哪些是风险、哪些超出当前周期范围。
尽可能让每个计划关联对应的史诗（Epic）。

How to build a trajectory roadmap (default)

如何构建轨迹型路线图（默认类型）

Declare the overarching objective of the journey.
List 2-5 phases or initiatives (sequenced or parallel).
Order by dependency and value — make sequencing explicit.
For each phase: expected outcome, dependencies, progress signal, risks.
Register what is a commitment, what is a risk, and what is out of scope.
Validate that the narrative is observable and stakeholder-ready.

明确整个流程的总体目标。
列出2-5个阶段或计划（有序或并行）。
按依赖关系和价值排序——明确排序逻辑。
针对每个阶段：预期成果、依赖关系、进度信号、风险。
记录哪些是承诺事项、哪些是风险、哪些超出范围。
验证内容是否可观测且适合展示给利益相关者。

How to build a quarterly roadmap (specific type)

如何构建季度型路线图（特定类型）

Same as above, with period objective (quarter) as the time boundary. Use when stakeholders expect a period-based view (common for product/exec audiences).

与上述步骤相同，以季度周期目标作为时间边界。适用于利益相关者期望基于周期查看的场景（常见于产品/高管受众）。

How to build a roadmap by epic

如何基于史诗构建路线图

Declare the epic objective.
Define phases or delivery waves.
Relate stories by phase.
Make unblocks, risks, and intermediate validations explicit.
Confirm that the roadmap guides execution without replacing plans.

明确史诗的目标。
定义阶段或交付波次。
按阶段关联用户故事。
明确障碍、风险和中间验证环节。
确认路线图可指导执行但不会替代详细计划。

Where to save

保存位置

Initiative/trajectory roadmap:
```
planning/<initiative>/roadmap.md
```
Quarterly roadmap:
```
planning/roadmaps/Q<N>-YYYY.md
```

计划/轨迹型路线图：
```
planning/<initiative>/roadmap.md
```
季度型路线图：
```
planning/roadmaps/Q<N>-YYYY.md
```

Collaborative work

协作工作

When the team has 2+ developers, the roadmap should:

Identify parallel tracks (e.g., Backend, Frontend, AI Engineering) so devs can work simultaneously
Define interface contracts between tracks to minimize blocking
Show which stories/phases can run in parallel in the timeline
Ask about team size and composition during roadmap creation

当团队有2名及以上开发者时，路线图应：

识别并行任务流（例如：后端、前端、AI工程），以便开发者可同时开展工作
定义任务流之间的接口约定，以减少阻塞
在时间线中显示哪些用户故事/阶段可并行执行
在路线图创建过程中询问团队规模和人员构成

Solo dev

独立开发者

For solo-dev work, parallelism does not apply at execution time. The parallel-track structure still helps for future-proofing — annotate tracks that could split if a second dev joins later, but pick a serial sequence for actual delivery. Mermaid

flowchart

(dependencies) fits solo work better than

gantt

(schedules).

对于独立开发者，执行阶段不存在并行性。但并行任务流结构仍有助于未来扩展——标注出若加入第二名开发者后可拆分的任务流，但实际交付需选择串行顺序。Mermaid的

flowchart

（依赖关系）比

gantt

（进度计划）更适合独立开发者的工作。

Chaining

技能衔接

At the end of the roadmap, offer only

/agile-epic

"Do you want me to run
```
/agile-epic
```
to decompose the first initiative into stories?"

Important: The roadmap identifies initiatives at a macro level. Each initiative should be decomposed via
/agile-epic
before execution.

路线图完成后，仅提供**

/agile-epic

**选项：

"是否需要我运行
```
/agile-epic
```
将首个计划分解为用户故事？"

重要提示：路线图从宏观层面识别计划。每个计划在执行前都应通过
/agile-epic
进行分解。

Template

模板

Use

templates/roadmap.md

from this skill as base.

以本技能中的

templates/roadmap.md

为基础模板。

Relationship with the flow

与工作流的关系

mermaid

flowchart LR
    A["/agile-intake"] --> B["/agile-roadmap"]
    B --> C["/agile-epic"]
    C --> D["/agile-story"]
    D --> E[execution]
    E --> F["/agile-status"]

This skill connects strategy and execution. For decomposition, use

/agile-epic

. For execution planning, use

/agile-story

mermaid

flowchart LR
    A["/agile-intake"] --> B["/agile-roadmap"]
    B --> C["/agile-epic"]
    C --> D["/agile-story"]
    D --> E[execution]
    E --> F["/agile-status"]

本技能连接战略与执行环节。如需分解计划，使用

/agile-epic

。如需进行执行规划，使用

/agile-story

。