Agent skill · Testing & QA

phx-work

Execute Elixir/Phoenix plan tasks with progress tracking. Use after /skill:phx-plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.

oliver-kriskagithub.com/oliver-kriskaGitHub ↗
claude-codeMIT
Install
npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-work --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 8 KB
Bundled scripts: none
Path: targets/pi/skills/phx-work/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Work Execute tasks from a plan file with checkpoint tracking and verification. ## Usage ``` /skill:phx-work .claude/plans/user-auth/plan.md /skill:phx-work .claude/plans/user-auth/plan.md --from P2-T3 /skill:phx-work --skip-blockers /skill:phx-work # Resumes most recent plan ``` ## Arguments - `<plan-file>` -- Path to plan file (optional, auto-detects recent) - `--from <task-id>` -- Resume from specific task (e.g., `P2-T3`) - `--skip-blockers` -- Continue past blocked tasks - `--continue` -- Resume IN_PROGRESS plan from checkboxes ## Iron Laws (NON-NEGOTIABLE) 1. **NEVER auto-proceed** to /skill:phx-review or any next workflow phase -- always ask the user what to do next 2. **AUTO-CONTINUE between plan phases** -- when Phase N completes, immediately start Phase N+1. Do NOT stop or ask for permission between phases. Only stop at BLOCKERS or when ALL phases are done. 3. **Plan checkboxes ARE the state** -- `[x]` = done; `[ ]` = pending unless the row is visibly tagged `[BLOCKED]`. No separate JSON state files. Resume by reading the plan. 4. **Verify after EVERY task** -- never skip verification 5. **Max 3 retries then BLOCKER** -- don't keep retrying forever 6. **Stage specific fil

What's inside
Steps it walks through
  1. Usage
  2. Arguments
  3. Iron Laws (NON-NEGOTIABLE)
  4. Step 1: Research Decision
  5. Step 2: Check Context (MANDATORY)
  6. Step 3: Load, Create Task List, and Resume
  7. Step 4: Execute Tasks
  8. Step 5: Completion
  9. Step 6: Check for Additional Plans
  10. Integration
  11. References
Ships with 5 files
  • references/error-recovery.md
  • references/execution-guide.md
  • references/file-formats.md
  • references/harness-patterns.md
  • references/resume-strategies.md
More from claude-elixir-phoenix
All skills →
About this skill
What does the phx-work skill do?

Execute Elixir/Phoenix plan tasks with progress tracking. Use after /skill:phx-plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.

How do I install it?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-work --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.

Keep going