Install any skill in seconds. Free to start, no credit card required.
Get Started Free →oliver-kriska/phx-full
Run a portable sequential plan-work-verify-review-compound lifecycle. Use optional generic workers only when Amp makes them available.
Passed 13 of 18 test cases with the skill, and 7 of 18 without it.
and 10 more in the full report
10 fixed6 passed either way4 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are running feature development on a Phoenix project for adding OAuth token refresh logic. Where should the plan file be written, and what exact file name and directory structure must be used? We usually put plans in docs/plans/oauth.md or root plan.md.
| Checked | Without skill | With skill |
|---|---|---|
| Places the plan artifact under the .claude/plans/ directory structure | Missed | Passed |
The instructions your model reads when the skill loads.
Run the portable lifecycle: discover → plan → work → verify → read-only review → compound. The filesystem is the state machine; no task API or named orchestrator is required.
/phx-full Add user authentication with magic links
/phx-full Background email jobs --max-cycles 5 --max-retries 2
If input is an existing .claude/plans/*/plan.md, do not re-plan. Ask for the
native phx-work workflow or execute its portable behavior in this session.
Defaults are --max-cycles 10, --max-retries 3, and --max-blockers 5.
mix commands
are the complete fallback. Record complexity and proposed depth, then wait for
the user's plan/implementation gate. Never auto-select a path that bypasses it.phx-plan skill when available, or
execute its portable research checklist and artifact format in this session.
Require .claude/plans/{slug}/plan.md. Present it and wait for approval before
implementation unless the user already explicitly authorized the full run.--max-retries N means at most N retries after
the initial attempt (N+1 total attempts for that task). Mark [BLOCKED] and
stop at --max-blockers.mix format --check-formatted, compile with warnings as
errors, focused tests during work, and the full relevant suite at this gate.
A failed gate appends FAIL and returns to WORKING only within the cycle limit.phx-review, or perform the same read-only,
changed-file review sequentially. Generic workers are optional. Review never
edits. Findings or failures become plan tasks and return to WORKING.test cases passed, vs 7 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.