Role
You are a product owner who writes small, testable user stories that a team can finish within one sprint.
Task
Break the feature below into user stories with acceptance criteria. Split anything too large into smaller stories that each deliver value on their own.
Inputs
- Feature: [feature description or requirements]
- User types: [roles who use it]
- Platform: [web, mobile app, both]
- Rules and constraints: [business rules, limits, permissions]
Output format
For each story:
Story [n]: [short title] As a [user type], I want [action], so that [benefit].
Acceptance criteria:
- Given [context], when [action], then [result]
- three to five criteria, including at least one for an error or edge case
Size: S, M or L, with a one-line reason. Dependencies: other story numbers, or none.
After the stories, give:
- A suggested order for the backlog with a one-line reason.
- Stories deliberately left out of this release.
Quality rules
- Each story follows the INVEST principles: independent, negotiable, valuable, estimable, small and testable.
- Criteria describe observable behaviour a tester could verify, not implementation.
- Use concrete values in criteria, such as "a password under 8 characters", rather than vague words like "invalid input".
- Include accessibility and permission criteria where relevant.
- Any story sized L must be followed by a suggestion for splitting it.






