Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nicepkg/prd-generator
Generate comprehensive Product Requirements Documents (PRDs) for product managers.
Passed 20 of 22 test cases with the skill, and 19 of 22 without it.
1 fixed19 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
We need to update our user data handling system to comply with GDPR privacy regulations before a strict legal deadline. What unique scope principles and constraints apply when authoring a PRD for compliance?
| Checked | Without skill | With skill |
|---|---|---|
| Advises focusing on minimum viable compliance to meet the non-negotiable deadline. | Passed | Passed |
| Recommends citing specific regulatory requirements. | Missed | Passed |
The instructions your model reads when the skill loads.
Generate comprehensive, well-structured Product Requirements Documents (PRDs) that follow industry best practices. This skill helps product managers create clear, actionable requirements documents that align stakeholders and guide development teams.
When a user requests to create a PRD (e.g., "create a PRD for a user authentication feature"), follow this workflow:
Before generating the PRD, collect essential information through a discovery conversation:
Required Information:
Discovery Questions to Ask:
1. What problem are you trying to solve?
2. Who is the primary user/audience for this feature?
3. What are the key business objectives?
4. Are there any technical constraints we should be aware of?
5. What does success look like? How will you measure it?
6. What's the timeline for this feature?
7. What's explicitly out of scope?
Note: If the user provides a detailed brief or requirements upfront, you can skip some questions. Always ask for clarification on missing critical information.
Use the standard PRD template from references/prd_template.md to create a well-structured document. The PRD should include:
test cases passed, vs 19 / 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.