Ruby on Rails is a Ruby workable choice for devtools / sdk. GreatCTO auto-detects both — adds the devtools archetype overlay, wires devtools-specific gates, and runs 34 specialist agents around your existing Ruby on Rails workflow.
GreatCTO reads your Gemfile and detects rails + devtools archetype from signals: imports, file structure, env vars, README hints.
Attaches the devtools archetype overlay: archetype-specific reviewer + compliance gates. Override if your specifics differ; the defaults are sensible for Ruby on Rails-style projects.
qa-engineer runs rubocop / rspec / brakeman; security-officer flags mass assignment + N+1 ORM queries; performance-engineer checks ActiveRecord query hot paths.
Bugs you've hit before in other Ruby on Rails projects (connection-pool exhaustion, ORM N+1 queries, retry storms) — the agent's Step 0 includes the prior detection order. MTTR drops 94 % on second occurrence (methodology).
$ cd my-rails-app && npx great-cto init ✓ scanning manifests… found manifest ✓ stack: rails (Ruby) ✓ archetype: devtools ⚠ archetype + stack combo is unusual — review overlay manually ✓ 34 agents ready $ /start "add devtools feature" ▸ architect drafting ARCH-devtools.md… ▸ pm decomposing into beads tasks… ⚐ gate:plan — your approval needed
Approve → 3 senior-devs run in parallel worktrees → 5 reviewers fan out in parallel → gate:ship → deploy. One real run walked stage-by-stage: /proof.
Ruby on Rails (Ruby) is not a typical fit for devtools / sdk. The archetype overlay still attaches, but you may want to override defaults more aggressively. Check the devtools archetype page for the typical stack list and decide if your case is the right tool / right archetype.
No black-box "AI does it all" loop. GreatCTO is a deterministic state machine — 8 stages, 22 nodes, 2 human gates. Every node maps to a real agent on GitHub. Inspect the state machine →
$ npx great-cto init
Free, MIT, runs locally. Works in Claude Code, Cursor, OpenAI Codex CLI, Aider, and Continue.