cto-review

Topics in the source

• /c-level-agents:cto-review — CTO Forcing Questions
• When to Run
• The Six CTO Questions
• 1. Scaling Cliff
• 2. Tech Debt Inventory
• 3. Team Scaling
• 4. Build vs Buy
• 5. SLO / Reliability

Command: /c-level-agents:cto-review Pressure-tests architecture and engineering scaling decisions. Six questions to surface the next scaling cliff before you hit it. 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 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. What's the top tech debt item, what's it costing per week, and when does it become blocking? For each open req, what's the ramp time and contribution model? 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. 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. What does this expose, and has cs-ciso-advi

This is an excerpt. Refer to the complete source and its current requirements.