CTO Advisor
Ongoing engineering leadership advice: team shape, on-call load, security baseline, DORA used right, tech debt funding, sized to your team.
Before & after
Same prompt, same agent — the only difference is the skill.
That's a classic architectural question. Microservices give you flexibility and independent scaling, but they add operational complexity. A monolith is simpler to manage but can become a bottleneck as your team grows. The answer really depends on your team size, deployment frequency, and whether you have pain points with the monolith. You could also consider a hybrid approach. Do you want to talk through your specific constraints and scale projections?
MONOLITH VS MICROSERVICES DECISION FRAMEWORK CURRENT STATE ASSESSMENT: • Team size: 12 engineers • Deployment frequency: 3-4 times per week • Monolith age: 18 months • Pain signals: Database lock contention on user-auth writes, occasional 500ms API latency spikes MICROSERVICES READINESS SCORE: 4/10 ✗ Team too small to support observability and debugging across services ✗ Deployment pipeline not mature enough (CI/CD is automated but no canary deploys) ✓ Clear service boundaries exist (auth, billing, content) ✗ No distributed tracing or circuit breakers in place RECOMMENDATION: STAY MONOLITHIC FOR NOW REASON: Microservices would introduce: • 2-3 more DevOps hires needed (20-30% org expansion) • 40+ hours per engineer learning distributed systems patterns • 6-12 month migration risk with zero product velocity INSTEAD - MODULARIZE THE MONOLITH: • Split auth logic into a separate internal package (dependency injection) • Extract billing into a separate database schema with read replicas • Set up a separate cache layer for auth (Redis) to relieve DB contention • Add database indexing on hot queries (auth writes) COST: 2-3 weeks of refactoring. Payoff: Eliminate the latency spike, gain 6 months of runway. REVISIT THIS DECISION AT: • 30 engineers, OR • Deployment frequency needs to exceed once per day per team, OR • Database locks return despite indexing That's when microservices ROI turns positive.
About this skill
Engineering leadership advice sized to your team, not to a company ten times bigger. It diagnoses the real bottleneck before recommending re-architecture or reorgs.
What it does
- Diagnoses slow delivery from commit-to-production time before blaming architecture
- Measures on-call load and cuts non-actionable alerts first
- Lists the security baseline to have before any SOC 2 work
- Shows when to add managers, SRE, or a platform team
- Frames tech debt as business cost so it gets funded
What you get
A direct recommendation with the team size at which it would change, a first 30-day step, and an optional ranked engineering risk review.
Best for
CTOs, VPs of Engineering, and technical founders running teams of 5 to 100 engineers.
SKILL.md preview
---
name: cto-advisor
description: Ongoing CTO-level advice on running engineering - team structure and when to add managers, SRE, or platform roles, tech debt strategy tied to business cost, DORA metrics used correctly, on-call load, security baseline and SOC 2 readiness, build vs buy posture, and architecture risk - calibrated to team size. Use when an engineering leader or technical founder asks "how should I structure a team of 25 engineers?", "how do I get the CEO to fund tech debt?", "our on-call is burning people out", "what security basics are we missing?", "should we track DORA metrics?", "when do we need a platform team?", or "what should a CTO worry about at our stage?".
---
… (sign up to view the full skill)More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.