Install any skill in seconds. Free to start, no credit card required.
Get Started Free →oliver-kriska/phx-plan
Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban).
Passed 9 of 16 test cases with the skill, and 6 of 16 without it.
and 2 more in the full report
5 fixed8 passed either way10 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before starting research on a feature with slug `user-billing`, where must the initial concern-track checklist be created?
| Checked | Without skill | With skill |
|---|---|---|
| The output specifies creating `.claude/plans/user-billing/scratchpad.md`. | Missed | Passed |
The instructions your model reads when the skill loads.
Plan a feature by researching the relevant Elixir/Phoenix concerns, then output a structured plan with checkboxes.
[ecto], [liveview], [oban] task routingmix compile/format/credo/test verification/phx-plan Add user avatars with S3 upload
/phx-plan .claude/plans/notifications/reviews/notifications-review.md
/phx-plan Implement notifications --depth deep
/phx-plan .claude/plans/auth/plan.md --existing
--depth quick|standard|deep = Planning depth (auto-detected)--existing = Enhance an existing plan with deeper research.claude/plans/{slug}/scratchpad.md with a concern-track checklisttest cases passed, vs 6 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.