phx-full
Run a portable sequential plan-work-verify-review-compound lifecycle. Use optional generic workers only when the runtime supports them.
npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-full --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.
# Full Phoenix Feature Development Run the portable lifecycle: discover → plan → work → verify → read-only review → compound. The filesystem is the state machine; no task API or named orchestrator is required. ## Usage ```text /phx-full Add user authentication with magic links /phx-full Background email jobs --max-cycles 5 --max-retries 2 ``` If input is an existing `.claude/plans/*/plan.md`, do not re-plan. Ask for the native `phx-work` workflow or execute its portable behavior in this session. Defaults are `--max-cycles 10`, `--max-retries 3`, and `--max-blockers 5`. ## Lifecycle 1. **DISCOVERING** — inspect relevant code, tests, prior solutions, and optional Tidewave evidence. Tidewave is optional; local files, logs, and `mix` commands are the complete fallback. Record complexity and proposed depth, then wait for the user's plan/implementation gate. Never auto-select a path that bypasses it. 2. **PLANNING** — invoke the runtime's native `phx-plan` skill when available, or execute its portable research checklist and artifact format in this session. Require `.claude/plans/{slug}/plan.md`. Present it and wait for approval before implementation unless the user already explicitly aut
- Usage
- Lifecycle
- Iron Laws
- Resume Ledger
- References
What does the phx-full skill do?
Run a portable sequential plan-work-verify-review-compound lifecycle. Use optional generic workers only when the runtime supports them.
How do I install it?
Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-full --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.