FastAPI is a Python natural fit for data platform. GreatCTO auto-detects both — adds the data-platform archetype overlay, wires data-platform-specific gates, and runs 83 specialist agents around your existing FastAPI workflow.
GreatCTO reads your pyproject.toml / requirements.txt and detects fastapi + data-platform archetype from signals: imports, file structure, env vars, README hints.
Attaches the data-platform archetype overlay: archetype-specific reviewer + compliance gates. Override if your specifics differ; the defaults are sensible for FastAPI-style projects.
qa-engineer runs mypy / ruff / pytest --cov; security-officer scans for SQL injection patterns common in ORMs (SQLAlchemy, Django ORM); performance-engineer profiles async patterns for I/O contention.
Bugs you've hit before in other FastAPI 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-fastapi-app && npx great-cto init ✓ scanning manifests… found pyproject.toml ✓ stack: fastapi (Python) ✓ archetype: data-platform ✓ overlay: applied ✓ 83 agents ready $ /start "add data-platform feature" ▸ architect drafting ARCH-data-platform.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 "data-platform feature" — auth first, schema validation, and the audit line the data-platform reviewer requires before gate:ship opens.
# app/routers/data_platform.py — drafted by senior-dev, reviewed by 5 agents
from fastapi import APIRouter, Depends
from app.auth import require_user # security-officer: auth before handler
from app.audit import audit_log # gate:data-platform: every decision logged
router = APIRouter(prefix="/data-platform")
@router.post("/")
async def create(payload: DataPlatformIn, user=Depends(require_user)):
result = await handle(payload, user) # qa-engineer: pydantic schema enforced
await audit_log(who=user.id, what="data-platform feature", confidence=result.confidence)
return resultdata-platform overlay.dbt warehouses with model contracts and lineage.
Airflow / Spark pipelines with PII detection in logs.
BI layers with GDPR retention enforcement.
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.