Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →product-on-purpose/deliver-user-stories
Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions.
Passed 17 of 22 test cases with the skill, and 3 of 22 without it.
and 11 more in the full report
14 fixed3 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Write a user story for a 'Dark Mode' toggle. Just say 'As a reader, I want a dark mode toggle.' We don't need the reason why.
| Checked | Without skill | With skill |
|---|---|---|
| The story includes a 'so that' benefit clause explaining the reason. | Missed | Passed |
The instructions your model reads when the skill loads.
User stories are concise descriptions of functionality from the user's perspective. They capture who needs something, what they need, and why - without prescribing how to build it. Good user stories enable teams to break large features into estimable, deliverable increments while maintaining focus on user value.
deliver-acceptance-criteriadeliver-edge-casesdeliver-prd first; stories should trace back to documented requirementsiterate-refinement-notesWhen asked to create user stories, follow these steps:
Understand the Feature Context Review the PRD or feature description. Understand the overall goal, target users, and scope boundaries. User stories should trace back to documented requirements.
Identify User Personas Determine which users interact with this feature. Each story should be written for a specific persona, not generic "users." Different personas may need different stories for the same feature.
Break Down by User Goal Decompose the feature into distinct user goals. Each story should deliver a complete, valuable capability - something the user can actually do when the story is done.
Write Story Statements Use the format: "As a [persona], I want [action] so that [benefit]." The benefit clause is critical - it explains why this matters and helps prioritize.
Define Acceptance Criteria Write specific, testable criteria using Given/When/Then format. Acceptance criteria define "done" - if all criteria pass, the story is complete.
Apply INVEST Criteria
test cases passed, vs 3 / 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.