Back to Details

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
If 
$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. If the user communicates in Portuguese, write in Portuguese with correct grammar and accents. If in English, write in English. When in doubt, ask the user which language to use. Templates are in English — translate headers and content to match.
生成的文档需使用用户的语言。如果用户使用葡萄牙语沟通，文档需使用语法正确、带有重音的葡萄牙语；如果使用英语，则用英语撰写。如有疑问，请询问用户使用哪种语言。模板为英文版本——需将标题和内容翻译为对应语言。

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
  • 独立、自包含的举措（单个Epic即可覆盖）
  • 无后续影响的单个Epic——直接使用
    /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)

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

  1. Declare the overarching objective of the journey.
  2. List 2-5 phases or initiatives (sequenced or parallel).
  3. Order by dependency and value — make sequencing explicit.
  4. For each phase: expected outcome, dependencies, progress signal, risks.
  5. Register what is a commitment, what is a risk, and what is out of scope.
  6. Validate that the narrative is observable and stakeholder-ready.
  1. 明确整个流程的核心目标。
  2. 列出2-5个阶段或举措（有序或并行）。
  3. 根据依赖关系和价值排序——明确展示顺序。
  4. 针对每个阶段：说明预期成果、依赖关系、进度信号及风险。
  5. 记录承诺事项、风险点及超出范围的内容。
  6. 确认路线图的表述清晰可查，且适合展示给利益相关者。

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

如何基于Epic构建路线图

  1. Declare the epic objective.
  2. Define phases or delivery waves.
  3. Relate stories by phase.
  4. Make unblocks, risks, and intermediate validations explicit.
  5. Confirm that the roadmap guides execution without replacing plans.
  1. 明确Epic的目标。
  2. 定义阶段或交付批次。
  3. 按阶段关联用户故事。
  4. 明确展示障碍消除、风险点及中间验证环节。
  5. 确认路线图仅用于指导执行，而非替代详细计划。

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名及以上开发人员时，路线图应：
  • 识别并行任务线（例如：Backend、Frontend、AI Engineering），以便开发人员同步工作
  • 定义任务线之间的接口契约，以减少阻塞
  • 在时间轴上展示哪些用户故事/阶段可以并行推进
  • 在创建路线图时询问团队规模及人员构成

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 
~/.agents/templates/roadmap.md
as base.
以
~/.agents/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
。