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 ## When NOT to Use - You need deeper, QA-ready Given/When/Then coverage for a single story or slice -> use `deliver-acceptance-criteria` - You need the feature-wide catalog of boundary conditions and failure scenarios -> use `deliver-edge-cases` - The feature itself is not yet specified -> use `deliver-prd` first; stories should trace back to documented requirements - You want refinement-session outcomes (estimates, scope decisions, open questions) -> use `iterate-refinement-notes` ## 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. **Identif...