Your coding agent ships code.
This is what checks it.
You write a spec. Your Claude Code builds against it, a second model from another family reads the same diff, and where they disagree you see the disagreement and decide. Three decisions stay yours — what gets built, how, and whether it ships — and spending caps refuse rather than warn. What lands is a repository you own and a URL that works. Requires Claude Code, or Codex for the skills and MCP server. Median $171 in tokens across seven products, measured 2026-07.
— downloads on npm15 industries · 60 products · 6 reusable pipelines
The 60 products collapse into 6 reusable build pipelines (CRUD vertical-SaaS, booking, CRM, dashboard, marketplace, content) — each ships through three default stops — one line in PROJECT.md takes it to one — then automated to a live URL. See how it works ↗
Describe it. Approve the spec. It ships.
Say what you want to build.
A dispatch app, a booking portal, a CRM, a dashboard — name the product and the industry. The architect and design-advisor draft the spec, data model and screens.
The spec is where you sign off.
You review the architecture and plan, and sign off. That is the second of three checkpoints by default — the brief came before it, the deploy comes after. At the lightest setting this one is a screen you read, not a form you sign.
Build → test → deploy, automated.
Scaffold, backend, frontend, integrations, generated tests and deploy run end to end — to a repo you own and a live URL.
Three commands carry the day. The rest wait until you need them.
/start "…"
A new product or a task in an existing project. It picks the workflow; three decisions stay yours — what to build, how, and whether it ships.
/inbox
Only the decisions waiting on you: gates, blockers, P0s. Nothing to scroll past.
/resume
Picks up where you left off — only what you already approved. A pending decision still waits for you.
The same three from the terminal, on Claude Code or Codex: great-cto run "…" · great-cto status · great-cto resume — add --host codex for Codex. All commands →
One screen for your work — it fills itself in.
great-cto board opens on Work: your tasks, the decisions waiting on you, and what already shipped. Cost, agents and reviewers are one click away under Tools. It runs on your machine — no account, no SaaS, telemetry off by default — and nothing on it shows an absence as a pass: a check that could not decide reads unverifiable, a cost nobody measured unmeasured.
One feature, end to end:
1h 26m and $3.40 in LLM cost.
A real run, fully public: spec → build → review → tests → merged PR. Every stage timestamped, every artifact links to a real GitHub PR — no screenshots, no marketing math.
median $171 · 70/100
The open benchmark built 7 products end to end: median $171 in tokens, median quality 70/100 (range 58–86). Reproduce it with scripts/bench-run.sh.
1h 26m · $3.40 LLM
Architect → plan → implementation → review → tests → merged PR. Wall-clock from prompt to ship, with one human signing the spec.
Timestamps, PRs, costs.
The full stage-by-stage timeline with public GitHub links. Walk the run on /proof →
Frequently asked.
What is GreatCTO?
What can it build?
How much is automated?
What does it cost?
Where does my data go?
How do I start?
Describe the product.
Ship the software.
Open source · MIT · self-hosted · your code stays on your machine