Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →stijnman/product-requirements-document
Write a clear product requirements document that defines the problem, scope, requirements, success measures, risks, and open questions.
Passed 13 of 22 test cases with the skill, and 7 of 22 without it.
and 11 more in the full report
8 fixed5 passed either way7 still failing2 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.
I need a complete product requirements document for adding a 'Pause Subscription' option to our direct-to-consumer mobile app. Customers currently cancel their recurring plans when traveling, so we want to let them pause for 1 to 3 months instead. Please generate a PRD draft containing problem framing, goals with success metrics, user personas and use cases, explicit scope boundaries, functional requirements, non-functional considerations, dependencies and risks, unresolved questions, and acceptance criteria.
| Checked | Without skill | With skill |
|---|---|---|
| Target metrics without known baselines are explicitly marked as provisional. | Missed | Passed |
| The draft uses placeholders for unverified delivery dates. | Missed | Passed |
The instructions your model reads when the skill loads.
Create a decision-ready product specification that explains why work matters, what must be delivered, what is out of scope, and how success will be evaluated without inventing unavailable facts.
Include: Problem, Goals and success measures, Users and use cases, Scope, Requirements, Non-functional considerations, Dependencies and risks, Open questions, and Acceptance criteria.
Do not fabricate customer evidence, market data, timelines, owners, technical commitments, or performance targets. Mark assumptions and placeholders visibly. Keep solution detail sufficient for alignment but leave implementation design to the relevant technical decision process.
| Situation | Response |
|---|---|
| Problem is not agreed | Produce a problem-framing draft and identify the missing decision. |
| Requirements conflict | Record the conflict, affected stakeholder, and trade-off rather than hiding it. |
| Metrics have no baseline | Propose a measurement plan and label the target provisional. |
| Scope is too broad | Split the document into a smallest viable release and deferred work. |
test cases passed, vs 7 / 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.