oliver-kriska/claude-elixir-phoenix / targets/pi/skills/phx-work
phx-work
VerifiedExecute 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.0 KB |
| references/error-recovery.md | markdown | 2.0 KB |
| references/execution-guide.md | markdown | 9.4 KB |
| references/file-formats.md | markdown | 1.7 KB |
| references/harness-patterns.md | markdown | 2.7 KB |
| references/resume-strategies.md | markdown | 2.3 KB |
references/file-formats.md
View on GitHub# Plan & Progress File Formats
## Plan File Format
Plans must follow this structure for parsing:
```markdown
# Plan: {Feature Name}
**Status**: IN_PROGRESS
**Created**: {date}
**Last Updated**: {date}
## Phase 1: {Phase Name} [COMPLETED|IN_PROGRESS|PENDING|BLOCKED]
- [x] [P1-T1][ecto] Completed task description — implementation note (key decisions, gotchas)
- [ ] [P1-T2][ecto] Pending task description
- [ ] [P1-T3][direct] [BLOCKED] Blocked task (remains unchecked)
## Phase 2: {Phase Name} [PENDING]
### Parallel: {Group Name}
- [ ] [P2-T1][liveview] Task that can run in parallel
- [ ] [P2-T2][liveview] Another parallel task
### Sequential
- [ ] [P2-T3][security] Task that depends on above
```
**Task format**: `- [ ] [Pn-Tm][concern] Description`; blocked tasks use `- [ ] [Pn-Tm][concern] [BLOCKED] Description`
- `[Pn-Tm]`: Phase n, Task m (for resume)
- `[concern]`: Guidance and verification annotation; never a worker identity
**Task ID format**: `[Pn-Tm]` - Phase n, Task m. Used for:
- Precise resume: `--from P2-T3`
- Blocker references
- Progress tracking
## Progress File Format
```markdown
# Progress: {Feature Name}
**Plan**: .claude/plans/{feature}/plan.md
**Started**: {date}
**Status**: IN_PROGRESS
## Session Log
### {date} {time}
**Task**: {description}
**Result**: PASS | FAIL
**Files**: {list of modified files}
**Started**: {date and time task execution began}
**Notes**: {any observations}
Progress evidence is append-only: never rewrite or delete prior Started, PASS, FAIL, retry, or blocker records.
---
### {date} {time}
**Task**: {description}
**Result**: FAIL
**Error**: {error message}
**Retry**: 1/3
**Resolution**: {what was tried}
```
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 |