Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fradser/to-spec
Turns the current conversation into a spec and publishes it to the project issue tracker, with no interview.
Passed 4 of 12 test cases with the skill, and 4 of 12 without it.
and 3 more in the full report
6 fixed2 passed either way11 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to turn our context on the OAuth2 refactor for the Acme Identity Service into a specification issue on GitHub. I haven't configured any issue label rules or tracker settings in this session yet. Please prepare the spec document.
| Checked | Without skill | With skill |
|---|---|---|
| Tells the user to execute `/mattpocock:setup-matt-pocock-skills` before proceeding. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill takes the current conversation context and codebase understanding and produces a spec (you may know this document as a PRD). Do NOT interview the user; just synthesize what you already know.
The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run /mattpocock:setup-matt-pocock-skills.
Do NOT interview the user; the spec is a synthesis of the conversation and codebase understanding already in context. Test at the highest existing seam, preferring one seam to many — check the seams with the user before writing.
Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.
Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.
Check with the user that these seams match their expectations.
ready-for-agent triage label - no need for additional triage.The problem that the user is facing, from the user's perspective.
The solution to the problem, from the user's perspective.
A LONG, numbered list of user stories. Each user story should be in the format of:
This list of user stories should be extremely extensive and cover all aspects of the feature.
test cases passed, vs 4 / 12 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.