
Deliver User Stories
Takes product requirements and breaks them down into properly formatted user stories with acceptance criteria. You get the standard "As a... I want... so that..." format plus Given/When/Then acceptance criteria for each story. It enforces INVEST principles (Independent, Negotiable, Valuable, Estimable, Small, Testable) and includes a quality checklist to catch common mistakes like embedding implementation details or skipping the benefit clause. Useful during sprint planning when you need to convert a PRD into actual tickets. The rigid structure might feel like overkill for simple features, but it keeps stories consistent across a team and forces you to think through what "done" actually means before engineering starts building.
- skills.sh installs
- 953
- GitHub stars
- 794
- last updated
- Aug 21, 2026
Install
$ npx -y skills add product-on-purpose/pm-skills --skill deliver-user-stories --agent claude-codeInstalls into .claude/skills of the current project.
Files
User Stories
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.
When to Use
- After PRD approval, when breaking down features for implementation
- During sprint planning to create actionable work items
- When writing tickets for engineering teams
- When communicating requirements to stakeholders in accessible terms
- When prioritizing a backlog based on user value
When NOT to Use
Sponsors
Details
- Repository
- github.com/product-on-purpose/pm-skills
- Categories
- Backend & APIs, Documentation, Code Review & Quality, Productivity & Planning
- First seen
- Jun 3, 2026
More from product-on-purpose/pm-skills
All 68- Deliver Edge Cases934
- Discover Competitive Analysis881
- Define Problem Statement878
- Define Hypothesis858
- Develop Adr842
- Deliver Launch Checklist834
- Develop Solution Brief830
- Define Opportunity Tree824
- Discover Interview Synthesis819
- Define Jtbd Canvas817
- Measure Dashboard Requirements801
- Measure Experiment Design801
- Deliver Release Notes797
- Develop Design Rationale793
- Foundation Persona792
- Measure Instrumentation Spec792
- Measure Experiment Results787
- Iterate Retrospective786
- Utility Mermaid Diagrams786
- Discover Stakeholder Summary779
- Foundation Okr Writer776
- Develop Spike Summary774
- Iterate Lessons Log767
- Iterate Pivot Decision767