deliver-user-stories

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# User Stories
3 
4User 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.
5 
6## When to Use
7 
8- After PRD approval, when breaking down features for implementation
9- During sprint planning to create actionable work items
10- When writing tickets for engineering teams
11- When communicating requirements to stakeholders in accessible terms
12- When prioritizing a backlog based on user value
13 
14## When NOT to Use
15 
16- You need deeper, QA-ready Given/When/Then coverage for a single story or slice -> use `deliver-acceptance-criteria`
17- You need the feature-wide catalog of boundary conditions and failure scenarios -> use `deliver-edge-cases`
18- The feature itself is not yet specified -> use `deliver-prd` first; stories should trace back to documented requirements
19- You want refinement-session outcomes (estimates, scope decisions, open questions) -> use `iterate-refinement-notes`
20 
21## Instructions
22 
23When asked to create user stories, follow these steps:
24 
251. **Understand the Feature Context**
26   Review the PRD or feature description. Understand the overall goal, target users, and scope boundaries. User stories should trace back to documented requirements.
27…