From elixir-phoenix
Executes Elixir/Phoenix plan tasks with progress tracking, mix compile/test verification after each step, and resume support via --continue or --from after /phx:plan.
npx claudepluginhub oliver-kriska/claude-elixir-phoenix --plugin elixir-phoenixThis skill uses the workspace's default tool permissions.
Execute tasks from a plan file with checkpoint tracking and verification.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Execute tasks from a plan file with checkpoint tracking and verification.
/phx:work .claude/plans/user-auth/plan.md
/phx:work .claude/plans/user-auth/plan.md --from P2-T3
/phx:work --skip-blockers
/phx:work # Resumes most recent plan
<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[x] = done, [ ] = pending.
No separate JSON state files. Resume by reading the plan.git add -A or git add .Ask the user for plans with >3 tasks:
This plan has {count} remaining tasks across {count} phases.
- Start working -- Begin immediately (familiar patterns)
- Quick research -- Read source files first (~10 min)
- Extensive research -- Web search + docs (~30 min)
Skip for plans with 3 or fewer simple tasks -- just start.
Split warning: Plans with >10 tasks risk 2-3 context compactions. Suggest splitting via
/phx:planif not already.
Read scratchpad and compound docs before writing any code. Skipping this causes rework — scratchpad captures dead-ends and decisions from planning that prevent taking wrong paths.
Read the scratchpad at .claude/plans/{slug}/scratchpad.md — it's short and has critical context.
Then search .claude/solutions/ for relevant keywords using Grep to find solved patterns.
Apply findings: skip dead-ends, follow decisions, reuse patterns. Always ask the user when a task's intent is ambiguous — never guess, corrections are expensive.
Read plan file, count [x] (completed) vs [ ] (remaining).
Find first unchecked task by [Pn-Tm] ID.
Create Claude Code tasks from ALL unchecked plan items using
TaskCreate. This gives real-time progress visibility in the UI:
For each unchecked `- [ ] [Pn-Tm] Description`:
TaskCreate({
subject: "[Pn-Tm] Description",
description: "Full task details from plan",
activeForm: "Implementing: Description"
})
Skip already-checked items ([x]) — don't create tasks for them.
Set up blockedBy dependencies between phases (Phase 2 tasks
blocked by Phase 1 tasks).
With --from P2-T3: Skip to that specific task.
See ${CLAUDE_SKILL_DIR}/references/resume-strategies.md for all resume modes.
Execute each unchecked task (- [ ] [Pn-Tm][agent] Description):
TaskUpdate({taskId, status: "in_progress"})[agent] annotation (see ${CLAUDE_SKILL_DIR}/references/execution-guide.md)mix format + mix compile --warnings-as-errors
(at phase end, also run mix test <affected> — see tiers below)[x] on pass, append
implementation note inline, AND
TaskUpdate({taskId, status: "completed"}). Example:
- [x] [P1-T3] Add user schema — citext for email, composite index on [user_id, status]
This survives context compaction; the plan is re-read on resume.Parallel groups: Tasks under ### Parallel: header spawn
as background subagents. See ${CLAUDE_SKILL_DIR}/references/execution-guide.md
for spawning pattern, prompt template, and checkpoint flow.
Verification tiers (scoped to minimize redundant runs):
mix compile --warnings-as-errors only
(format is checked by PostToolUse hook automatically)mix compile --warnings-as-errors + mix test <affected_files> + mix credo --strict
(scope tests: mix test test/path/to_affected_test.exs — NOT full suite)project_eval
(create record, fetch, verify -- see execution-guide.md)mix test (full suite — run ONCE at the end, not per-phase)Token efficiency: Do NOT narrate each verification step. Execute tool calls directly without "Let me now run..." preamble. Only narrate when explaining a non-obvious decision or reporting a failure.
Linter note: The PostToolUse hook checks formatting but does NOT modify files. Run
mix formatexplicitly during verification steps or before committing.
Summarize results with AskUserQuestion:
Implementation complete! {done}/{total} tasks finished. {count} files modified across {count} phases.
Options: 1. Run review (/phx:review) (Recommended),
2. Get a briefing (/phx:brief — understand what was built),
3. Commit changes (/commit), 4. Continue manually.
With blockers: list them, offer Replan (/phx:plan),
Review first (/phx:review), or Handle myself.
If blockers remain, auto-write HANDOFF to scratchpad:
### [HH:MM] HANDOFF: {plan name}
Status: {done}/{total} tasks. Blockers: {list}.
Next: {first unchecked task ID and description}.
Key decisions: {brief list from this session}.
Include context beyond checkboxes for fresh session resume.
NEVER auto-start /phx:review or any other phase.
Check for other pending plans after completion:
Use Glob to find other plan files matching .claude/plans/*/plan.md.
If pending plans exist, inform the user. Do NOT auto-start.
/phx:plan → /phx:work (YOU ARE HERE) → /phx:review → /phx:compound
↑ ASK USER before each transition
${CLAUDE_SKILL_DIR}/references/execution-guide.md -- Task routing, parallel execution, verification${CLAUDE_SKILL_DIR}/references/resume-strategies.md -- Resume modes and state persistence${CLAUDE_SKILL_DIR}/references/file-formats.md -- Plan and progress file formats${CLAUDE_SKILL_DIR}/references/error-recovery.md -- Error handling and blockers${CLAUDE_SKILL_DIR}/references/harness-patterns.md -- Critic-refiner pattern for debugging loops