Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nicepkg/requirements-specification
Master requirements gathering, user story writing, acceptance criteria definition, and scope management. Transform insights into clear, actionable specifications.
Passed 7 of 22 test cases with the skill, and 15 of 22 without it.
1 fixed19 passed either way1 still failing1 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.
What is the recommended maximum page count and required content focus for the Executive Summary section of a comprehensive product requirements document?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies a maximum length of 1 page for the executive summary. | Missed | Passed |
| Includes business goals or success metrics among the executive summary elements. | Passed | Passed |
The instructions your model reads when the skill loads.
Transform customer insights into clear, detailed specifications that engineering can build from. Master user story writing, define acceptance criteria, and manage scope ruthlessly.
I - Independent (minimal dependencies) N - Negotiable (details can be discussed) V - Valuable (delivers customer value) E - Estimable (team can estimate effort) S - Small (can complete in 1-2 sprints) T - Testable (clear success criteria)
As a [user role]
I want [action/capability]
So that [benefit/outcome]
Acceptance Criteria:
Given [context]
When [user action]
Then [expected result]
Bad Story:
As a user
I want a better dashboard
So that I can see my data
Problem: Too vague, not testable, too large
Good Story:
test cases passed, vs 15 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.