technical-roadmap-planning

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Technical Roadmap Planning Skill

技术路线图规划技能

Step 1 — Gather Inputs

步骤1 — 收集输入信息

Before defining initiatives, collect:

Business objectives for the period (OKRs, product strategy, growth targets).
Tech debt inventory — known architectural problems, reliability gaps, security risks.
Reliability data — incident history, SLA breaches, on-call burden.
Team capacity — headcount, planned leave, hiring timeline.
Dependencies — migrations, third-party deprecations, compliance deadlines.

Ask the user to provide or confirm these inputs before proceeding.

在定义行动计划之前，先收集以下内容：

业务目标（OKRs、产品策略、增长目标）。
技术债务清单——已知的架构问题、可靠性缺口、安全风险。
可靠性数据——事件历史记录、SLA违约情况、值班负担。
团队产能——人员数量、计划休假、招聘时间表。
依赖项——迁移工作、第三方服务弃用、合规截止日期。

在继续下一步前，请让用户提供或确认这些输入信息。

Step 2 — Define Initiatives

步骤2 — 定义行动计划

For each initiative, capture:

Initiative: <name>
Problem:    <what is broken or missing — one sentence>
Metric:     <how success is measured — must be quantifiable>
Effort:     <S | M | L | XL>  (S=days, M=weeks, L=1-2 months, XL=quarter+)
Impact:     <Low | Medium | High | Critical>
Dependencies: <other initiatives or teams this blocks or is blocked by>

Example:

Initiative: Database connection pooling
Problem:    Under peak load, the API exhausts the DB connection limit, causing 503s.
Metric:     Zero connection-limit errors in staging load test at 2× current peak traffic.
Effort:     S
Impact:     High
Dependencies: None

针对每个行动计划，记录以下信息：

Initiative: <名称>
Problem:    <存在的问题或缺失的内容——一句话描述>
Metric:     <成功衡量标准——必须可量化>
Effort:     <S | M | L | XL> （S=天，M=周，L=1-2个月，XL=季度及以上）
Impact:     <Low | Medium | High | Critical>
Dependencies: <此计划依赖或阻塞的其他计划/团队>

示例：

Initiative: Database connection pooling
Problem:    Under peak load, the API exhausts the DB connection limit, causing 503s.
Metric:     Zero connection-limit errors in staging load test at 2× current peak traffic.
Effort:     S
Impact:     High
Dependencies: None

Step 3 — Prioritise (Impact / Effort Matrix)

步骤3 — 优先级排序（影响/工作量矩阵）

Plot each initiative on a 2×2 grid and apply the priority rules:

Impact
  High │ Quick Wins ★ │ Strategic Bets ◆
       │ (do now)     │ (plan carefully)
       ├──────────────┼──────────────────
  Low  │ Fill-ins     │ Avoid / defer
       │ (if capacity)│
       └──────────────┴────────────────
          Low Effort      High Effort

Priority	Quadrant	Action
1	High Impact + Low Effort	Schedule immediately
2	High Impact + High Effort	Plan with milestones
3	Low Impact + Low Effort	Fill between larger items
4	Low Impact + High Effort	Defer or remove

Mark compliance/security items as non-negotiable regardless of quadrant.

将每个行动计划绘制在2×2网格中，并应用以下优先级规则：

Impact
  High │ Quick Wins ★ │ Strategic Bets ◆
       │ (do now)     │ (plan carefully)
       ├──────────────┼──────────────────
  Low  │ Fill-ins     │ Avoid / defer
       │ (if capacity)│
       └──────────────┴────────────────
          Low Effort      High Effort

优先级	象限	行动
1	高影响 + 低工作量	立即安排
2	高影响 + 高工作量	制定里程碑计划
3	低影响 + 低工作量	在大型项目间隙填充执行
4	低影响 + 高工作量	推迟或取消

无论处于哪个象限，合规/安全相关项均标记为不可协商。

Step 4 — Sequence

步骤4 — 排序

Apply dependency ordering:

Initiatives with no dependencies come first.
Identify the critical path: the longest chain of dependent initiatives.
Avoid starting more than 2 large initiatives in parallel (context switching cost).

按照依赖关系排序：

无依赖的行动计划优先启动。
识别关键路径：最长的依赖行动计划链。
避免同时启动超过2个大型行动计划（减少上下文切换成本）。

Step 5 — Milestone Definition

步骤5 — 里程碑定义

Break each Large or XL initiative into milestones with binary (done/not-done) completion criteria:

Initiative: Event-driven order processing
Milestone 1: Outbox pattern implemented and tested in staging        — Week 2
Milestone 2: Consumer deployed; order events flowing in staging       — Week 4
Milestone 3: Production rollout complete; legacy sync path removed    — Week 6

将每个大型（L）或超大型（XL）行动计划拆分为具有二元（完成/未完成）验收标准的里程碑：

Initiative: Event-driven order processing
Milestone 1: Outbox pattern implemented and tested in staging        — Week 2
Milestone 2: Consumer deployed; order events flowing in staging       — Week 4
Milestone 3: Production rollout complete; legacy sync path removed    — Week 6

Step 6 — Output: Roadmap Table

步骤6 — 输出：路线图表格

Produce the roadmap in this format:

markdown

undefined

按以下格式生成路线图：

markdown

undefined

Technical Roadmap — Q2 2025

#	Initiative	Impact	Effort	Owner	Target	Status
1	DB connection pooling	High	S	Platform	Week 1	Planned
2	Event-driven orders	High	L	Backend	Week 6	Planned
3	Remove legacy auth	Medium	M	Backend	Week 4	Planned
4	Upgrade Go 1.26	Low	S	Platform	Week 2	Planned

#	Initiative	Impact	Effort	Owner	Target	Status
1	DB connection pooling	High	S	Platform	Week 1	Planned
2	Event-driven orders	High	L	Backend	Week 6	Planned
3	Remove legacy auth	Medium	M	Backend	Week 4	Planned
4	Upgrade Go 1.26	Low	S	Platform	Week 2	Planned

Dependencies

Item 3 (Remove legacy auth) is blocked by item X (New auth rollout, owned by product).

Item 3 (Remove legacy auth) is blocked by item X (New auth rollout, owned by product).

Risks

Item 2 requires DB schema changes; coordinate with DBA team.

Item 2 requires DB schema changes; coordinate with DBA team.

Out of Scope This Quarter

GraphQL federation migration (deferred to Q3 — too high effort)

undefined

GraphQL federation migration (deferred to Q3 — too high effort)

undefined