Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →golbin/prd
Create or update an evidence-backed living Product Requirements Document (PRD) and, when useful, linked context and phase execution files under tasks/.
4 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 4 comparable cases; this report requires 8.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need a basic email notification system for user password resets. Please write a PRD for this password reset notification service. To be thorough, include multi-channel fallback support (SMS, WhatsApp, Push), machine-learning send-time optimization, and custom template WYSIWYG editors.
| Checked | Without skill | With skill |
|---|---|---|
| The scope excludes speculative features such as machine-learning send-time optimization. | Missed | Passed |
| The output reports the document file path using the tasks/prd-password-reset-notification.md convention. | Missed | Passed |
| The output explicitly reports open decisions requiring user input. | Missed | Passed |
The instructions your model reads when the skill loads.
Keep the user's outcome, target design, and remaining work in one document. Planning-only requests end with the PRD; continue implementation when already requested.
Read the project evidence needed to identify the problem, affected users, and observable success conditions. Ask about missing decisions that materially affect scope or correctness; record reasonable assumptions for other details.
Choose the simplest design that meets the need, correcting the foundation when necessary. Follow Unix philosophy: focused, composable parts, explicit interfaces, and policy and side effects at boundaries. APIs and internal tools also serve users, including developers and operators.
Include compatibility, recovery, retries, or migration for concrete user, data, contract, or failure risks. Keep temporary mechanisms removable with a retirement condition. Avoid speculative features and abstractions.
Update an existing PRD when available. Otherwise follow the requested location or
project convention, defaulting to tasks/prd-<feature>.md.
Include:
Use only the sections the task needs. Split out linked files when detailed evidence or independent work warrants it. Validation items should identify the behavior or contract to prove and a suitable check allowed by project rules.
Preserve user edits and completed work. Update the plan as evidence changes;
test cases passed with the skill
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.