Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →joonghyun-lee-frieren/oma-plan
Use this skill when the request is non-trivial and should be planned before editing code.
Passed 16 of 22 test cases with the skill, and 5 of 22 without it.
and 15 more in the full report
13 fixed3 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/21/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to introduce Stripe subscription billing to our application, which will touch the backend payment handlers, database schemas, and frontend UI. Could you generate a structured implementation plan covering the objectives, phase ordering, task dependencies, risk factors, and verification steps?
| Checked | Without skill | With skill |
|---|---|---|
| The response formats the output using the section headers Goal, Phase Plan, Task Breakdown, Risks, and Validation. | Missed | Passed |
| The phase plan sequences frontend and backend changes in distinct phases. | Passed | Passed |
| The validation section defines verification checkpoints. | Passed | Passed |
The instructions your model reads when the skill loads.
Read the workflow when this skill applies. For code work, follow the guard contract first. Design and implementation require separate user turns. Only the owning main conversation writes code. Missing evidence is unknown; honest failure is a valid outcome.
test cases passed, vs 5 / 22 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.