plan
Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.
npx skills add oliver-kriska/claude-elixir-phoenix --skill plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- What Makes /phx:plan Different from /plan
- Usage
- Arguments
- Workflow
- --existing Mode (Deepening)
- Iron Laws
- Integration with Workflow
- Notes
- CRITICAL: After Writing the Plan
- References (DO NOT read — for human reference only)
What does the plan skill do?
Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.
How do I install it?
Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From oliver-kriska/claude-elixir-phoenix, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.