User stories describe a feature from the point of view of the person who uses it, and this skill writes them for you in Claude from a rough idea or a full product requirements document. You get stories a developer can pick up, with acceptance criteria clear enough to test and edge cases written down before they turn into bugs.
How do you write good user stories?
A good story names a real user, one thing they want to do, and why it matters to them. It is small enough to finish in a sprint and can be tested when it’s done. The skill checks every story against the INVEST criteria (independent, negotiable, valuable, estimable, small, testable) and rewrites the ones that fail. When a story is too large, it splits it by workflow step, by rule or by user type, so each piece still delivers something a user can see.
When the idea doesn’t say who the users are or what permissions they have, the skill asks before writing. A story for “the admin” and a story for “a team member on the basic plan” are different stories.
A user story template with acceptance criteria
Many people searching for a user story template really need the acceptance criteria that go with it. Each story here comes with criteria in Given/When/Then form, covering the main path and the unhappy ones: empty input, no permission, a failed payment, a slow network. Under them sit the edge cases worth discussing and a short out-of-scope note, so the team agrees on what the story does not include.
A backlog order, not estimates
The skill suggests an order to build the stories in, based on what unblocks the rest and what delivers value soonest, with the reason for each. It leaves story points and hours to your team, since only they know their pace.
FAQ
What can I give it as input?
A one-line feature idea, meeting notes, a customer request, a PRD or a spec. The more it knows about users and rules, the fewer questions it asks.
Can I paste the stories into Jira or Linear?
Yes. The output is plain Markdown with a title, description and acceptance criteria per story, which pastes cleanly into either tool.
Does it write technical tasks too?
It focuses on user-facing stories. It can list the technical tasks a story implies when you ask, kept separate from the stories themselves.
