You don't have a CTO. Or you are the CTO — and you're the bottleneck. Plug great_cto into Claude Code. Architecture, TDD, code review, QA, security, deploy — one pipeline. Two decisions per feature.
7 agents · 10 archetypes · 15 commands · 12-angle review · 13 compliance frameworks
You never write the architecture doc, the QA report, or the release notes. You approve, or you don't.
Everything you need day-to-day lives behind three commands. Everything else runs on a trigger — you don't remember it, you don't invoke it.
great_cto is a Claude Code plugin. No dashboards. No SaaS. File-based configs under
.great_cto/
— inspect and edit anything.
Each angle runs as a separate pass with its own rubric. Findings rated P0 / P1 / P2 — P0 blocks the gate until you decide.
You don't pay for what you don't need. /start
picks the scale automatically — override with "make it deep" or "this is just a quick fix".
npx great-cto init
scans your codebase, picks the right archetype, and wires compliance gates automatically.
Each archetype gets a default security tier — signals raise it automatically during implementation.
Archetype is a starting point, not a verdict. The real tier is set by signals —
conditions detected in your diff as it lands. A web-service
that adds Stripe and touches auth/
gets the same depth of review as commerce does by default.
senior-dev watches your diff and emits
SECURITY_SIGNAL: lines. Signals only upgrade — never downgrade.
.great_cto/ — inspect and edit anything.
/start "fix typo" runs 1 agent in ~5 min.
/start "add Stripe subscriptions" runs 5 agents in ~45 min.
You never pay for what you don't need.
/audit — it finds gaps in your existing repo and creates a task backlog.
Use that even if you never run the full pipeline.
Two decisions per feature. The rest happens in the pipeline.