user-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
Security Assessment
About user-story
The 'user-story' skill helps product managers, designers, and engineers create structured user stories using Mike Cohn's format with Gherkin-style acceptance criteria. It focuses on translating user needs into actionable development work with clear outcomes and testable conditions, promoting shared understanding across teams. This skill ensures stories capture who benefits, what they want to achieve, and why it matters, while providing concrete scenarios to validate success.
Main capabilities include generating well-formed user stories with defined user personas, desired outcomes, and constraints. It provides a consistent format combining Mike Cohn's 'As a/I want/So that' template with Gherkin 'Given/When/Then' acceptance criteria. The skill supports backlog grooming, sprint planning, and communication of value to engineering and QA teams. Optional helper scripts allow deterministic Markdown template generation for consistent story documentation.
Typical use cases involve converting product requirements or PRDs into actionable user stories, writing stories for new features or systems in software projects, and establishing quality standards for user story creation. Target users include product managers, UX designers, developers, and QA engineers who need testable and outcome-focused stories to guide development work.
FAQ
What is the main purpose of the 'user-story' skill?
Its main purpose is to create structured user stories combining Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with clear outcomes and testable conditions.
Can this skill be used for technical debt or refactoring tasks?
No, it is intended for user-facing features and value-driven stories. Technical debt or refactoring should be handled as engineering tasks.
Is there a template or script to help generate stories consistently?
Yes, an optional CLI helper script can generate a deterministic Markdown stub for consistent story documentation.
Who benefits from using this skill?
Product managers, UX designers, developers, and QA engineers benefit by having clear, testable, and outcome-focused user stories to guide development.
What should I do if I don’t have enough context to write a story?
Run discovery interviews or problem validation work first to gather user personas, understand the problem, define desired outcomes, and identify constraints.
Install user-story
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
deanpeters/product-manager-skills