Review architecture and engineering growth plans through six questions covering capacity limits, technical debt, staffing, build-versus-buy costs, reliability, and security. Produce a structured verdict and three next steps before committing to major technical decisions.
中文简介正在准备中。当前显示英语简介。
/c-level-agents:cto-review [plan] — Architecture and scaling interrogation. Tech debt, scaling cliffs, team scaling, build-vs-buy. Use when committing to an architecture, planning for 10x load, or weighing a rebuild against a vendor.
安装前可以查看交给 AI 代理的指令内容。
Command: /c-level-agents:cto-review <plan>
Pressure-tests architecture and engineering scaling decisions. Six questions to surface the next scaling cliff before you hit it.
Where does the current architecture break, in terms of users / requests / data volume?
What's the top tech debt item, what's it costing per week, and when does it become blocking?
python ${CLAUDE_PLUGIN_ROOT}/vendor/c-level-advisor/cto-advisor/scripts/tech_debt_analyzer.py
For each open req, what's the ramp time and contribution model?
python ${CLAUDE_PLUGIN_ROOT}/vendor/c-level-advisor/cto-advisor/scripts/team_scaling_calculator.py
Why are we building this instead of buying it — and what's the 3-year TCO of each?
What are the SLOs for this system and what's the current error budget burn?
engineering/slo-architect for SLO design.What does this expose, and has cs-ciso-advisor signed off?
# CTO Review: <plan>
**Date:** YYYY-MM-DD
## Scaling Cliff
- Current capacity: <metric>
- Break point: <metric>
- Headroom: X months at current growth
## Tech Debt
- Top item: <description>
- Cost per week: $X or N eng-hours
- Blocking date estimate: <date>
## Team
- Open reqs: N
- Median ramp: X months
- Contribution model: <pairing / squad / area>
## Build vs Buy
- 3-year build TCO: $X
- 3-year buy TCO: $X
- Strategic fit: <core / context>
- Decision: BUILD | BUY
## Reliability
- SLO defined: yes / no
- Error budget burn: X% (target < Y%)
## Security
- cs-ciso sign-off: ✅ / ❌
## Verdict
🟢 SHIP | 🟡 SHARPEN | 🔴 BLOCK
## Next Steps
[3 concrete actions]
/c-level-agents:ciso-review — mandatory if data surface changes/c-level-agents:cfo-review — for build-vs-buy > $100K/c-level-agents:execute — quarterly plan/c-level-agents:boardroom — for architecture pivotscs-cto-advisorcto-advisor../../../engineering/slo-architect/Version: 1.0.0
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.
中文简介正在准备中。当前显示英语简介。
Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.
中文简介正在准备中。当前显示英语简介。
Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.
中文简介正在准备中。当前显示英语简介。
Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.
中文简介正在准备中。当前显示英语简介。
Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.
中文简介正在准备中。当前显示英语简介。
Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.
中文简介正在准备中。当前显示英语简介。