wowprompt

User Stories With Acceptance Criteria

A set of user stories broken down from a feature, each with Given-When-Then acceptance criteria and a size estimate. Use it before sprint planning so the team agrees on what done means.

Numbered user stories in the as-a, I-want, so-that format, each followed by three to five Given-When-Then acceptance criteria
The output this prompt produced, unedited.

The prompt

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:

  1. A suggested order for the backlog with a one-line reason.
  2. 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.
user storiesacceptance criteriagiven when thenagile backlogsprint planning

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity