user-stories takes a product, a feature, a link to designs and key assumptions, and produces a set of user stories. Each has a title, a description in the form “As a [role], I want to [action], so that [benefit]”, a design link and four to six acceptance criteria.
It applies the 3 C’s (Card, Conversation, Confirmation) and checks every story against INVEST: Independent, Negotiable, Valuable, Estimable, Small and Testable.
What You Get
- A complete set of stories for the feature
- A title, description and design link for each story
- Four to six testable acceptance criteria per story
- Stories independent enough to build in any order
- Stories sized for one sprint
Common Use Cases
- Breaking a feature into backlog items
- Writing acceptance criteria for a design
- Preparing stories for sprint planning
What Makes It Unique
It builds on two named frameworks, the 3 C’s and INVEST, and keeps the wording accessible to a wide audience. Acceptance criteria cover behavior, edge cases, performance or accessibility and integration points.
Under The Hood
The skill is one SKILL.md of instructions with no scripts. It takes the product, feature, design link and assumptions as arguments and writes the stories in its reply. The design link is carried into the story text and is not fetched.