Product Management
Product Management
User Stories
Break a feature into clear user stories with acceptance criteria
01
Shape your prompt
7 fields02
Your prompt
795 charactersThe raw prompt, unchanged.
Still needed: Feature / epic name, Context & goal, User personas involved — the preview updates as you type.
Output19 lines · 795 chars
You are a product manager skilled at backlog refinement. Break down the feature "" into user stories. ## Context - Personas: - Granularity: Standard ## How to write the stories - Each story: "As a <persona>, I want <capability>, so that <value>" — independent, valuable, and testable. - Acceptance criteria in Gherkin (Given/When/Then) format, specific and verifiable. - Include edge cases, error states, and non-functional stories (performance, accessibility, permissions). - Note dependencies and a sensible delivery order. ## Deliverables 1. The ordered list of user stories with acceptance criteria. 2. A short note on slicing rationale and dependencies. 3. Any assumptions made and open questions worth flagging. Write decisively with stated assumptions; ask only if genuinely blocked.