🌐 phoenix × web-service

Ship web service / api on Phoenix without losing weeks to compliance.

Phoenix is a Elixir natural fit for web service / api. GreatCTO auto-detects both — adds the web-service archetype overlay, wires web-service-specific gates, and runs 34 specialist agents around your existing Phoenix workflow.

$ npx great-cto init 🌐 See archetype →

What changes when GreatCTO joins your Phoenix project

Detection → overlay → gates → reviewers.

1 · DETECT

Stack + archetype

GreatCTO reads your mix.exs and detects phoenix + web-service archetype from signals: imports, file structure, env vars, README hints.

2 · OVERLAY

Archetype pack

Attaches the web-service archetype overlay: OWASP API Top-10, GDPR data-minimization, SLO + error-budget gates. Override if your specifics differ; the defaults are sensible for Phoenix-style projects.

3 · GATES

Phoenix-aware reviewers

qa-engineer runs mix test --cover / credo --strict; security-officer audits Ecto query injection + Phoenix CSRF; performance-engineer profiles BEAM scheduler + Ecto pool.

4 · MEMORY

Cross-project lessons

Bugs you've hit before in other Phoenix 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).

First 10 minutes

Concrete walkthrough.

$ cd my-phoenix-app && npx great-cto init
✓ scanning manifests… found manifest
✓ stack: phoenix (Elixir)
✓ archetype: web-service
✓ overlay: applied
✓ 34 agents ready

$ /start "add authenticated REST endpoint"
▸ architect drafting ARCH-web-service.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.