Next.js is a TypeScript workable choice for cli tool. GreatCTO auto-detects both — adds the cli-tool archetype overlay, wires cli-tool-specific gates, and runs 34 specialist agents around your existing Next.js workflow.
GreatCTO reads your package.json and detects nextjs + cli-tool archetype from signals: imports, file structure, env vars, README hints.
Attaches the cli-tool archetype overlay: archetype-specific reviewer + compliance gates. Override if your specifics differ; the defaults are sensible for Next.js-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 Next.js 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-nextjs-app && npx great-cto init ✓ scanning manifests… found package.json ✓ stack: nextjs (TypeScript) ✓ archetype: cli-tool ⚠ archetype + stack combo is unusual — review overlay manually ✓ 34 agents ready $ /start "add cli-tool feature" ▸ architect drafting ARCH-cli-tool.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.
Next.js (TypeScript) is not a typical fit for cli tool. The archetype overlay still attaches, but you may want to override defaults more aggressively. Check the cli-tool 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.