21 Agents

Each agent is a focused specialist with fresh context. Orchestrators coordinate parallel work. Specialists review one domain at a time. Mechanical agents handle compression and verification.

Orchestrators · 4

• parallel-reviewer · opus · high
  Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
• planning-orchestrator · opus · high
  Orchestrates feature planning by coordinating specialized agents. Internal use - spawns research, architecture, and review agents. Use proactively when comprehensive planning needed.
• security-analyzer · opus · high
  Security audit specialist for Elixir/Phoenix - authentication, authorization, input validation, OWASP vulnerabilities. Use proactively when implementing auth or handling user input.
• workflow-orchestrator · opus · high
  Orchestrates the full agentic workflow cycle (plan → work → review). Internal use by /phx:full command.

Specialists · 13

• call-tracer · sonnet · medium
  Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
• deep-bug-investigator · sonnet · medium
  Deep bug investigation using 4 parallel subagents (reproduction, root cause, impact, fix strategy). Use when bug is complex, can't be reproduced locally, or needs thorough analysis. Spawns fresh-context subagents for each investigation track.
• deployment-validator · sonnet · medium
  Deployment configuration validator - releases, Docker, Kubernetes, Fly.io. Use proactively before deploying to production.
• ecto-schema-designer · sonnet · medium
  Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
• elixir-reviewer · sonnet · medium
  Expert Elixir/Phoenix code reviewer - idioms, patterns, performance, conventions. Use proactively after writing Elixir code.
• hex-library-researcher · sonnet · medium
  Researches Elixir libraries on hex.pm. Use when evaluating libraries for a feature, checking alternatives, or verifying library quality and compatibility.
• iron-law-judge · sonnet · medium
  Checks code for Iron Law violations using pattern analysis. Use proactively after code changes or as part of review.
• liveview-architect · sonnet · medium
  LiveView architecture specialist - component structure, real-time patterns, streams vs assigns, async patterns. Use proactively when planning interactive features.
• oban-specialist · sonnet · medium
  Oban worker specialist - reviews idempotency, error handling, and production safety. Use proactively when implementing or reviewing background jobs.
• otp-advisor · sonnet · medium
  OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
• phoenix-patterns-analyst · sonnet · medium
  Analyzes codebase for existing Phoenix patterns, contexts, module structure, scopes, plugs, and routing. Use proactively when planning features to understand current conventions.
• requirements-verifier · sonnet · medium
  Cross-check implementation against task requirements (Linear issue, GitHub issue, plan, spec). Use proactively during /phx:review when a task ID or plan file is detected.
• testing-reviewer · sonnet · medium
  Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.

Mechanical · 4

• context-supervisor · haiku · low
  Compresses multi-agent output into consolidated summaries to prevent context exhaustion. Generic — works for any orchestrator. Use after sub-agents complete and before parent synthesis.
• verification-runner · haiku · low
  Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, ex_check), test commands, and custom aliases. Use proactively after code changes.
• web-researcher · haiku · low
  Fetches and extracts information from web sources efficiently. Optimized for ElixirForum, HexDocs, and GitHub. Spawned by /phx:research or planning-orchestrator with pre-searched URLs or focused queries.
• xref-analyzer · haiku · low
  Analyze module dependencies and context boundaries using mix xref. Use proactively before major refactors or when reviewing architectural changes.