Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nicepkg/writing-product-specs
Use when asked to design a new feature or project
Passed 17 of 24 test cases with the skill, and 12 of 24 without it.
and 6 more in the full report
8 fixed9 passed either way4 still failing3 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.
When writing the product requirements for our in-app credit card payment update, we decided that crypto payments and invoice billing will not be supported. In which section of the product spec should these explicit exclusions be placed, and why?
| Checked | Without skill | With skill |
|---|---|---|
| The response places explicit exclusions in the Non-requirements section. | Missed | Passed |
| The response states that Non-requirements prevent scope creep. | Missed | Passed |
The instructions your model reads when the skill loads.
Write comprehensive product specification documents that clearly communicate what we're building, why we're building it, and how we'll know it's successful. Document everything stakeholders need to understand: the problem context, target audience, requirements, success criteria, and tradeoffs. Give them a complete picture of the feature or project.
Assume the reader is a skilled product person or engineer, but knows nothing about this specific feature or the problem domain. Assume they need clear context to understand the "why" behind the work.
Announce at start: "I'm using the writing-product-specs skill to create the product specification."
Context: This should be run when designing a new feature or planning a project that needs clear requirements documentation.
Save specs to artifacts named spec--MM-DD-YYYY.md (or as requested by the user).
Core principle: Product specifications are detailed descriptions of the features and functionality of a product. They are used to communicate the requirements of the product to the development team.
Use this skill when:
Follow this process to elicit the necessary information and compose a comprehensive product specification.
Ask questions to understand the feature or project. Gather information about:
test cases passed, vs 12 / 24 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.