Skip to content

oliver-kriska/claude-elixir-phoenix / plugins/elixir-phoenix/skills/full

Deliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review. Use when several coordinated workflows or contexts must ship together. NOT for an existing plan; use /phx:work.

FileKindSize
SKILL.mdskill md9.0 KB
references/cycle-patterns.mdmarkdown4.5 KB
references/example-run.mdmarkdown2.3 KB
references/execution-steps.mdmarkdown4.0 KB
references/safety-recovery.mdmarkdown2.1 KB

references/safety-recovery.md

View on GitHub
# Safety Rails & Recovery

## Resume from Interruption

When resuming an interrupted workflow:

1. **Read progress file** `.claude/plans/{slug}/progress.md`
2. **Check plan checkboxes** in `.claude/plans/{slug}/plan.md`:
   - Count `[x]` (completed) vs `[ ]` (pending) tasks
   - Find the first unchecked task to resume from
3. **Validate artifacts**:
   - Ensure plan and progress files exist
   - Ensure completed tasks match checkboxes in plan
4. **Continue from first unchecked task**

Example resume:

```bash
/phx:work --continue
# Reads the IN_PROGRESS plan, e.g. .claude/plans/magic-link-auth/plan.md
# Finds first unchecked task: P2-T3
# Resumes from P2-T3
```

Or resume from specific task:

```bash
/phx:work .claude/plans/magic-link-auth/plan.md --from P2-T3
```

## Ralph Wiggum Integration

For fully autonomous execution, use with Ralph Wiggum Loop:

```bash
/ralph-loop:ralph-loop "/phx:full {feature}" --completion-promise "DONE" --max-iterations 50
```

This enables:

- Automatic recovery from context window limits
- Persistent execution across sessions
- True autonomous completion

## Automatic Stops

The cycle stops automatically when:

1. All tasks complete successfully
2. Max cycles reached
3. Max blockers reached
4. Fatal compilation error (unrecoverable)
5. Test suite completely broken (>50% failing)

## Human Checkpoints

`/phx:full` has no checkpoint flag. For a human review between phases, run
`/phx:plan`, `/phx:work` and `/phx:review` separately instead.

## Rollback Points

The commit offered after each phase (see `/phx:work` Commit Strategy) is the
rollback point:

```bash
# If something goes wrong
git log --oneline  # Find last good commit
git reset --hard {commit}
```

## State Recovery

Plan checkboxes ARE the state. If progress file is missing,
the plan still contains all state needed to resume:

```bash
# Check current progress from plan checkboxes
COMPLETED=$(grep -c '\[x\]' .claude/plans/${SLUG}/plan.md)
TOTAL=$(grep -c '\[.*\] \[P' .claude/plans/${SLUG}/plan.md)
echo "Progress: $COMPLETED / $TOTAL tasks complete"

# Resume from first unchecked task
/phx:work .claude/plans/${SLUG}/plan.md
```
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall