deliver-user-stories

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # 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 ## Instructions When asked to create user stories, follow these steps: 1. **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. 2. **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. 3. **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. 4. **Write Story Statements** Use the format: "As a [persona], I want ...