Remix is a TypeScript natural fit for cms / content platform. GreatCTO auto-detects both — adds the cms archetype overlay, wires cms-specific gates, and runs 83 specialist agents around your existing Remix workflow.
GreatCTO reads your package.json and detects remix + cms archetype from signals: imports, file structure, env vars, README hints.
Attaches the cms archetype overlay: archetype-specific reviewer + compliance gates. Override if your specifics differ; the defaults are sensible for Remix-style projects.
qa-engineer runs tsc --strict / eslint / vitest --coverage; security-officer checks for prototype pollution + XSS sinks; performance-engineer reviews bundle size + cold-start times.
Bugs you've hit before in other Remix 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-remix-app && npx great-cto init ✓ scanning manifests… found package.json ✓ stack: remix (TypeScript) ✓ archetype: cms ✓ overlay: applied ✓ 83 agents ready $ /start "add cms feature" ▸ architect drafting ARCH-cms.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.
This is the shape of what senior-dev drafts for "cms feature" — auth first, schema validation, and the audit line the cms reviewer requires before gate:ship opens.
// app/routes/cms.tsx — drafted by senior-dev, reviewed by 5 agents
import { json, type ActionFunctionArgs } from '@remix-run/node';
import { requireUser } from '~/lib/auth.server'; // security-officer: auth first
import { auditLog } from '~/lib/audit.server'; // gate:cms: every decision logged
export async function action({ request }: ActionFunctionArgs) {
const user = await requireUser(request);
const body = schema.parse(await request.json()); // qa-engineer: zod enforced
const result = await handle(body, user);
await auditLog({ who: user.id, what: 'cms feature', confidence: result.confidence });
return json(result);
}cms overlay.Content platforms with schema.org structured data.
UGC sites with DMCA safe-harbor and moderation.
Publishing flows tuned for Core Web Vitals.
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. Built as a Claude Code plugin — install with one command.
Eight stages, two human gates, four memory layers. Why this exact shape, and what I tried that didn't work.
One run, one feature, from prompt to merged PR. Time, cost, and gate-by-gate breakdown — no marketing math.
Regex vs LLM-based archetype detection, the false-positive count, and why I keep rejecting the obvious fix.
The bottleneck in agentic SDLC isn't model quality — it's process governance. Here's the state machine that closes the gap.