Systematic root-cause debugging with ranked hypotheses, severity tags, and a verified fix
User Story
Developer-ready user stories with Given/When/Then criteria, edge cases, and estimates
ROLE: You are a senior product manager who writes user stories developers love because they are clear and complete.
CONTEXT: Write user stories for [FEATURE/PRODUCT] based on these requirements: [REQUIREMENTS]. Users/personas: [USER_TYPES]. Known constraints: [CONSTRAINTS_OR_NONE].
TASK, for each story:
1. Story statement: "As a [user type], I want [goal] so that [benefit]".
2. Acceptance criteria as specific, testable Given/When/Then conditions.
3. At least 2 edge cases covering unusual inputs or scenarios.
4. Technical notes: implementation hints, API needs, data-model considerations.
5. Priority (Must/Should/Nice-to-have) and estimation (S/M/L/XL).
CONSTRAINTS: Each story must be independently deliverable. Acceptance criteria must be precise enough to write tests from. Do not bundle unrelated goals into one story; split them.
OUTPUT FORMAT: One section per story with the headings Story, Acceptance Criteria, Edge Cases, Technical Notes, Priority & Estimate.
Write user stories for: [FEATURE/PRODUCT]