Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →borghei/spec-to-repo
Translate product specs (PRDs, user stories) into a ship-ready repo plan: ticket decomposition, branch strategy, and PR sequencing.
Passed 17 of 22 test cases with the skill, and 9 of 22 without it.
and 9 more in the full report
8 fixed9 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
What ticket size classification applies to a well-scoped feature task estimated at 2 days of engineering effort?
| Checked | Without skill | With skill |
|---|---|---|
| Classifies tasks estimated at 1 to 3 days as M. | Missed | Passed |
The instructions your model reads when the skill loads.
A delivery-focused skill that bridges product spec to repository work. Where PRD-writing skills focus on what to build, this skill focuses on how to break it down for execution — the ticket decomposition, branch strategy, PR sequencing, and acceptance criteria that make a spec actually ship.
Before generating the repo plan, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.