| name | full |
| description | Deliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review. Use when several coordinated workflows or contexts must ship together. NOT for an existing plan; use /phx:work. |
| effort | high |
| argument-hint | <feature description> [--codex] |
Full Phoenix Feature Development
Execute complete Elixir/Phoenix feature development autonomously: research patterns,
plan with specialist agents, implement with verification, Elixir code review.
Cycles back automatically if review finds issues.
Usage
/phx:full Add user authentication with magic links
/phx:full Real-time notification system with Phoenix PubSub
/phx:full Background job processing for email campaigns --max-cycles 5
/phx:full Add magic-link auth --codex
Wrong input guard: if the argument is a path to an existing plan file
(.claude/plans/*/plan.md), do NOT re-plan it. Say so and run /phx:work {path}
instead — the plan phase already happened.
Flags
--codex — Codex CLI joins the review panel on every review
cycle, matching /phx:review --codex.- Requires the
codex CLI. A missing CLI degrades to a SKIPPED note —
the cycle never fails.
- Consensus findings (flagged by a Claude agent codex) are
marked HIGH CONFIDENCE.
