oliver-kriska/claude-elixir-phoenix / plugins/elixir-phoenix/skills/work
work
VerifiedExecute Elixir/Phoenix plan tasks with progress tracking. Use after /phx:plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.3 KB |
| references/error-recovery.md | markdown | 1.7 KB |
| references/execution-guide.md | markdown | 10.0 KB |
| references/file-formats.md | markdown | 1.4 KB |
| references/harness-patterns.md | markdown | 3.0 KB |
| references/resume-strategies.md | markdown | 1.9 KB |
references/resume-strategies.md
View on GitHub# Resume Strategies
## How State Works
**Plan checkboxes ARE the state.** No separate JSON state files.
- `[x]` = completed
- `[ ]` = pending
- Phase status `[COMPLETED|IN_PROGRESS|PENDING]` tracks phase progress
- BLOCKERs in progress file track failed tasks
## Resume Modes
### Default: Auto-detect
```
/phx:work # Find most recent IN_PROGRESS plan, resume from first [ ]
```
### From Specific Task
```
/phx:work .claude/plans/auth/plan.md --from P2-T3
```
Skips directly to P2-T3 regardless of earlier unchecked tasks.
### Skip Blockers
```
/phx:work .claude/plans/auth/plan.md --skip-blockers
```
Continues past tasks that previously failed with BLOCKER status.
## Resume from Interrupted Session
On resume, the plan file itself shows progress:
```markdown
## Phase 1: Schema Design [COMPLETED]
- [x] [P1-T1][ecto] Create users migration
- [x] [P1-T2][ecto] Add indexes
## Phase 2: Context Module [IN_PROGRESS]
- [x] [P2-T1][direct] Generate context
- [ ] [P2-T2][ecto] Add password_hash <-- Resumes here
- [ ] [P2-T3][direct] Implement register_user/1
```
No state file to parse. Just find first `[ ]` and continue.
## Consistency Check
On resume, validate:
- All tasks before the target should be `[x]` in plan
- If earlier tasks are unchecked, warn and ask user:
- Skip them (mark as done)?
- Go back and complete them?
- Something else?
## Idempotent Task Execution
Tasks should be safe to re-execute:
| Task Type | Idempotent Approach |
|-----------|---------------------|
| Migration | Use `create_if_not_exists` or check schema |
| Schema | Write complete module, don't patch |
| Context | Write/replace function entirely |
| LiveView | Write complete component module |
| Test | Write complete test module |
| Route | Check route existence before adding |
If re-executing a task creates duplicate code, the task was not
idempotent. Write whole modules, not patches.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |