phxplan

# Plan Elixir/Phoenix Feature Plan a feature by spawning Elixir specialist agents, then output structured plan with checkboxes. ## What Makes /phx:plan Different from /plan 1. Spawns Elixir specialist agents for research 2. Plans with `[ecto]`, `[liveview]`, `[oban]` task routing 3. Checks for Iron Law compliance in the plan 4. Includes `mix compile/format/credo/test` verification 5. Understands Phoenix context boundaries ## Usage ``` /phx:plan Add user avatars with S3 upload /phx:plan .claude/plans/notifications/reviews/notifications-review.md /phx:plan Implement notifications --depth deep /phx:plan .claude/plans/auth/plan.md --existing ``` ## Arguments - `$ARGUMENTS` = Feature description, review file, or existing plan - `--depth quick|standard|deep` = Planning depth (auto-detected) - `--existing` = Enhance an existing plan with deeper research ## Workflow 1. **Gather context** — File path (skip to agents), brainstorm interview.md (skip clarification), clear description, or vague 2. **Clarify if vague** — Ask questions ONE at a time (skip if brainstorm interview.md exists with Status: COMPLETE) 3. **Detect depth** — Auto-detect quick/standard/deep 4. **Runtime context** (Tidewave) — Gather live schemas, routes, and warnings before spawning agents (see planning-orchestrator) 5. **Spawn research agents** — Selective, parallel, based on need. Create a Claude Code task per agent for progress visibility: `TaskCreate({subject: "{Agent} research", activeFor...