Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/to-prd
Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Passed 6 of 16 test cases with the skill, and 5 of 16 without it.
and 2 more in the full report
5 fixed3 passed either way10 still failing4 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.
We're adding rate limiting to our API gateways. When identifying seams for testing in the PRD workflow, how many integration seams should we ideally aim for across the codebase?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends a single high-level architectural testing seam. | Missed | Passed |
The instructions your model reads when the skill loads.
Use when this workflow matches the user request: Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
_Source: mattpocock/skills (MIT)._This skill takes the current conversation context and codebase understanding and produces 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 — run /setup-matt-pocock-skills if not.
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 PRD, 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 5 / 16 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.