Try “Claude Code skills”, “MCP servers for Cursor” or “Codex” · Esc to close

great_cto 🤖 Agent Free

A 70-agent pipeline that runs Claude Code through staged, human-gated product development

Subagent collections · Free ★ 102 · MIT · updated 2026-10-02

7.5editor score
Visit great_cto ↗
GitHub stars
102
Stars this week
–
Forks
13
Licence
MIT
Last push
2026-10-02
Maintainer
avelikiy
Installgit clone https://github.com/avelikiy/great_cto && cp great_cto/*.md ~/.claude/agents/

Third-party subagents & agents run with your permissions. Read the source before installing, and prefer pinned versions.

Works with

About great_cto

What it does

great_cto is an orchestration layer on top of Claude Code that turns a single prompt into a full staged product-development pipeline, run by 70 specialist agents rather than one generalist session. An independent model reviews each stage before the next one builds on it, and three decisions are deliberately kept in human hands: what gets built, how it gets built, and whether to deploy.

What is inside

The pipeline moves through problem framing and a written brief, a human checkpoint to approve requirements, an architecture and design phase, a second human checkpoint to approve the approach, implementation (scaffold, backend, frontend, tests, review, security), a third checkpoint to approve deployment, and finally live deployment. Each stage carries its own verification gate and cost tracking, and spending caps refuse further spend outright rather than just warning. Slash commands (/save, /resume, /review, /spec, /poc, /release, /trace) let you checkpoint, resume, and audit a run in progress.

Works with

Claude Code is the primary target; Codex is supported through a controlled host runtime. Requires Node.js 18.17 or later.

How to install or connect

npx great-cto init

Then, inside Claude Code:

/start "describe your product"

Maintenance and safety

MIT licensed with notably active development (1,600+ commits), 102 stars, and 5 open issues at last check. The human-approval checkpoints before implementation and before deployment are a meaningful safety feature for an agent pipeline that otherwise runs with significant autonomy.

Who should use it

Solo developers or small teams who want Claude Code to drive an entire build from spec to deployed URL, but with explicit approval gates and cost controls rather than letting dozens of agents run unsupervised.

claude-code-plugin subagent-pipeline agentic-coding cost-tracking spec-driven

Pros

  • Structures Claude Code into a staged pipeline (brief, architecture, implementation, deployment) with an independent model reviewing each stage and three explici
  • Spending caps refuse rather than silently warn, and commands like /save, /resume, /review and /trace give visibility and control over a long-running multi-agent

Cons

  • 70-agent orchestration adds real token/API cost on top of whatever model you run it with, and the staged checkpoints mean it suits deliberate builds more than q

Similar subagents & agents

All subagent collections →

wshobson/agents 🤖 AgentFree

Large plugin marketplace of specialist subagents, skills and commands for Claude Code

★ 40k · +192 this week

Power Platform Skills 🤖 AgentOpen source

Official Microsoft plugins for building Power Platform apps, pages and flows with Claude Code or Copilot

★ 947 · +19 this week

8.0 Visit ↗

Popular searches