CTO Review
/cs:cto-review <plan> — Architecture and scaling interrogation.
Before & after
Same prompt, same agent — the only difference is the skill.
That's a good planning question to think about. Scaling can be challenging as your business grows. You'll want to consider your database capacity, server resources, and how your API handles increased load. Think about whether your architecture has bottlenecks. You might need to add more servers or optimize queries. Caching can help too. Different scaling strategies work for different architectures. It really depends on your current setup and growth trajectory. Have you thought about what the main scaling challenges might be?
ARCHITECTURE INTERROGATION CRITICAL SCALING CLIFF: Database: PostgreSQL single-instance, 150GB at 10x load (current: 15GB) Issue: Replication lag at scale; connection pool exhausts at 3000 QPS (you hit 2900 at 8x) Fix urgency: IMMEDIATE before Series A (breach likely at 6x within 2 quarters) DECISION POINT: Upgrade to managed Postgres + read replicas (4 weeks, 18k) vs rebuild on Firestore (8 weeks, design risk) Recommendation: Postgres scaling path preserves schema; you own the upside SECONDARY CLIFFS: 1. API Gateway rate-limiter (per-user, not global) — add sliding-window counters (3 days) 2. Cache invalidation strategy (currently TTL-only) — add event-driven purge (2 days) 3. Message queue depth (SQS at 80% max depth today) — forecast 220% at 10x; add worker pool (1 week) TEAM SCALING BLOCKER: Your on-call rotation (2 people) cannot handle 10x incident volume. Add 1 engineer to SRE role before scaling 5x. REB UILT ESTIMATE: 12 weeks to 10x-safe architecture. Start now. Do not fundraise on current architecture.
About this skill
name: cto-review description: Use when /cs:cto-review <plan> — Architecture and scaling interrogation.
Cto Review
/cs: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.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the cto-review skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Cto Review; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: cto-review
description: Use when committing to an architecture, planning for a 10x load increase, or weighing a system rebuild against a vendor solution.
version: 1.0.0
category: Business & Ops / Executive Advisory
author: AgentVolt
license: proprietary
tags:
- business-ops
- executive-advisory
---
# Cto Review
Runs a CTO-level architecture and scaling interrogation of a technical plan — probing tech debt, scaling cliffs, team-scaling implications, and build-versus-buy tradeoffs before committing resources.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Gc Review
/cs:gc-review <plan> — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
Caio Review
/cs:caio-review <plan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring.
Boardroom
/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis.
Context Engine
Loads and manages company context for all C-suite advisor skills.