Updated: 4 November 2026

Turn a feature idea into user stories

This prompt turns a feature into stories in the As a user, I want, so that form, each with acceptance criteria, edge cases and out-of-scope notes.

text-user-story-writer — chatgpt — 51 words

Turn this feature idea into user stories:

[DESCRIBE FEATURE]

Users: [USER TYPES]

Write stories in the form "As a [user], I want [goal], so that [benefit]." For each, add acceptance criteria, edge cases and what is out of scope. Split anything bigger than a few days of work into smaller stories.

Edit in the builder Copy & open ChatGPT ↗Copy & open Gemini ↗Copy & open Claude ↗

Ask for acceptance criteria in "Given, When, Then" form so testers know what done means.

Get a better result

What you will get

User stories in “As a…, I want…, so that…” form, each with acceptance criteria, edge cases and what is out of scope, with anything bigger than a few days split into smaller stories.

Why it works

User stories keep work focused on the person using it, and the template forces a reason for every feature. Acceptance criteria, edge cases and out-of-scope notes are where misunderstandings get caught before building. Splitting large stories keeps each one small enough to finish and test in a sprint.

Common mistake

The “so that” repeats the goal.

Fix: The benefit should be the reason, such as “so that I don’t miss a payment”, not “so that I can see the dashboard”.

Also watch for

The acceptance criteria cannot be tested. Ask for Given, When, Then form, as the tip says, so testers know what done means.
Edge cases are generic. Give real limits, such as file sizes or user roles, so the edge cases match your product.

Try a variation: story map

Ask for the stories arranged as a story map: the user’s steps across the top and stories under each, with the smallest first release marked.

Still not right? Reply with this

Rewrite the acceptance criteria for every story in Given, When, Then form, and split any story with more than five criteria into two.