Write User Stories With Acceptance Criteria

This prompt converts a loose feature idea into a backlog-ready set of user stories, each paired with testable Given-When-Then acceptance criteria. Reach for it when you have a concept but need it structured the way engineers and QA can actually pick up. The persona-action-benefit format keeps every story tied to a real user need rather than a technical task, and the edge-case flag at the end surfaces the unknowns that usually derail sprints later.

What you can expect back

Story 1
As a mobile reader, I want to save an article to my reading list with one tap, so that I can return to it later without searching.
- Given I'm viewing an article, When I tap the bookmark icon, Then it fills in and the article appears in my list.
- Given an article is already saved, When I tap the icon again, Then it's removed and the icon returns to outline state.
- Given I have no network, When I tap save, Then the action queues and a 'will sync' indicator shows.

Story 2
As a commuter, I want saved articles available offline, so that I can read in a tunnel.
- Given an article is saved on wifi, When the device goes offline, Then the full text and images render from cache.

Edge cases / open questions
- What is the storage cap per device, and what gets evicted first?
- How do we resolve a save/unsave conflict made on two devices while offline?

Illustrative example — your results will vary by tool and inputs.

Get sharper results

• 01Include the user's context and motivation in the description, not just the feature — 'finish reading in a tunnel' produces sharper acceptance criteria than 'offline mode.'
• 02Ask it to keep stories vertically sliced (each independently shippable) so they map cleanly to sprint planning rather than producing one giant epic.
• 03If you already know your non-functional requirements like performance or accessibility, name them so they become acceptance criteria instead of getting missed.
• 04Run the edge-case list back through the prompt as a second pass — answering those questions often spawns one or two stories you'd otherwise discover mid-sprint.
• 05Tell it your team's definition of done (e.g. 'must include analytics events') so criteria reflect your actual gate, not a generic one.

Adapt it for your case