Back to Details

cto-review

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/cs:cto-review — CTO Forcing Questions

/cs:cto-review — CTO核心质询问题

Command: 
/cs:cto-review <plan>
Pressure-tests architecture and engineering scaling decisions. Six questions to surface the next scaling cliff before you hit it.
命令： 
/cs:cto-review <plan>
对架构与工程扩展性决策进行压力测试。通过六个问题，帮助你在遭遇扩展瓶颈前提前发现问题。

When to Run

适用场景

  • Before approving a major architecture change
  • Before doubling the engineering team
  • Before a build-vs-buy decision > $100K/year
  • When a system is showing reliability stress (SLOs missed)
  • Before committing to a new platform / language / DB
  • 批准重大架构变更前
  • 工程团队规模翻倍前
  • 年投入超10万美元的自建vs采购决策前
  • 系统出现可靠性压力时（未达成SLO）
  • 承诺采用新平台/语言/数据库前

The Six CTO Questions

六个CTO核心问题

1. Scaling Cliff

1. 扩展瓶颈

Where does the current architecture break, in terms of users / requests / data volume?
  • Be specific. "It breaks at 10× current load because the primary DB writes saturate."
  • If you don't know, run a load test before deciding.
当前架构在用户量/请求量/数据量达到什么程度时会崩溃？
  • 需具体说明。例如：“当负载达到当前10倍时，主数据库写入饱和，系统崩溃。”
  • 若不确定，决策前先进行负载测试。

2. Tech Debt Inventory

2. 技术债务清单

What's the top tech debt item, what's it costing per week, and when does it become blocking?
bash
python ../../../skills/cto-advisor/scripts/tech_debt_analyzer.py
最优先级的技术债务是什么？每周造成的成本是多少？何时会成为阻塞性问题？
bash
python ../../../skills/cto-advisor/scripts/tech_debt_analyzer.py

3. Team Scaling

3. 团队扩张

For each open req, what's the ramp time and contribution model?
bash
python ../../../skills/cto-advisor/scripts/team_scaling_calculator.py
针对每个空缺岗位，新成员的上手周期和贡献模式是什么？
bash
python ../../../skills/cto-advisor/scripts/team_scaling_calculator.py

4. Build vs Buy

4. 自建vs采购

Why are we building this instead of buying it — and what's the 3-year TCO of each?
  • If "we want control" or "it's not that hard" — push back.
  • If the answer is "this is our core moat," build.
我们为什么选择自建而非采购？两者的3年总拥有成本（TCO）分别是多少？
  • 若理由是“我们想要控制权”或“这不难”，需重新考量。
  • 若理由是“这是我们的核心护城河”，则选择自建。

5. SLO / Reliability

5. SLO/可靠性

What are the SLOs for this system and what's the current error budget burn?
  • Without an SLO, you can't reason about reliability tradeoffs.
  • See 
    engineering/slo-architect
    for SLO design.
该系统的SLO是什么？当前错误预算消耗情况如何？
  • 没有SLO，就无法合理权衡可靠性相关的取舍。
  • 可查看
    engineering/slo-architect
    获取SLO设计相关内容。

6. Security & Compliance Surface

6. 安全与合规范围

What does this expose, and has cs-ciso-advisor signed off?
  • Architecture decisions are compliance decisions.
  • Loop in cs-ciso-advisor before commit.
该决策会暴露哪些风险？是否已获得cs-ciso-advisor的签字确认？
  • 架构决策等同于合规决策。
  • 提交决策前需与cs-ciso-advisor沟通确认。

Workflow

工作流程

  1. Run the tech debt analyzer + team scaling calculator
  2. Define the scaling-cliff hypothesis explicitly
  3. Cross-check with cs-ciso-advisor for security implications
  4. Apply the verdict
  1. 运行技术债务分析器和团队扩张计算器
  2. 明确提出扩展瓶颈假设
  3. 与cs-ciso-advisor交叉核对安全影响
  4. 执行最终决策

Output Format

输出格式

markdown
undefined
markdown
undefined

CTO Review: <plan>

CTO审查：<plan>

Date: YYYY-MM-DD
日期： YYYY-MM-DD

Scaling Cliff

扩展瓶颈

  • Current capacity: <metric>
  • Break point: <metric>
  • Headroom: X months at current growth
  • 当前容量：<指标>
  • 崩溃临界点：<指标>
  • 余量：按当前增长速度可维持X个月

Tech Debt

技术债务

  • Top item: <description>
  • Cost per week: $X or N eng-hours
  • Blocking date estimate: <date>
  • 最优先级项：<描述>
  • 每周成本：X美元或N个工程师工时
  • 预计阻塞日期：<日期>

Team

团队情况

  • Open reqs: N
  • Median ramp: X months
  • Contribution model: <pairing / squad / area>
  • 空缺岗位数：N
  • 平均上手周期：X个月
  • 贡献模式：<结对编程/小组制/领域负责>

Build vs Buy

自建vs采购

  • 3-year build TCO: $X
  • 3-year buy TCO: $X
  • Strategic fit: <core / context>
  • Decision: BUILD | BUY
  • 3年自建总拥有成本：X美元
  • 3年采购总拥有成本：X美元
  • 战略契合度：<核心业务/周边业务>
  • 决策：自建 | 采购

Reliability

可靠性

  • SLO defined: yes / no
  • Error budget burn: X% (target < Y%)
  • 是否已定义SLO：是/否
  • 错误预算消耗：X%（目标<Y%）

Security

安全情况

  • cs-ciso sign-off: ✅ / ❌
  • cs-ciso签字确认：✅ / ❌

Verdict

最终结论

🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK
🟢 执行 | 🟡 优化 | 🔴 阻塞

Next Steps

下一步行动

[3 concrete actions]
undefined
[3项具体行动]
undefined

Routing

关联路由

  • /cs:ciso-review
    — mandatory if data surface changes
  • /cs:cfo-review
    — for build-vs-buy > $100K
  • /cs:execute
    — quarterly plan
  • /cs:boardroom
    — for architecture pivots
  • /cs:ciso-review
    — 若数据范围发生变化则为必填项
  • /cs:cfo-review
    — 适用于年投入超10万美元的自建vs采购决策
  • /cs:execute
    — 季度计划审查
  • /cs:boardroom
    — 适用于架构转型决策

Related

相关资源

  • Agent: 
    cs-cto-advisor
  • Skill: 
    cto-advisor
  • SLO: 
    ../../../../engineering/slo-architect/
Version: 1.0.0
  • Agent: 
    cs-cto-advisor
  • Skill: 
    cto-advisor
  • SLO: 
    ../../../../engineering/slo-architect/
版本： 1.0.0