How to use the User Story Generator
This generator turns three short phrases into an agile user story and a set of acceptance criteria. It fills the template As a [role], I want to [action], so that [benefit], then writes 3 or 5 Given / When / Then scenarios around your action. It is for product owners, founders and developers who want a clean first draft for the backlog.
Step by step
-
Name the role
Type the type of user in Role, who is this for? Use a role such as store manager, not a person's name. Until you type anything, the tool shows an example built from store manager.
-
Describe the action
Type what they want to do in Action, what do they want to do? Start with a verb, for example export a sales report. The story adds I want to in front of it, so do not type those words yourself.
-
Give the benefit
Type why it matters in the Benefit field, for example share it with head office. It is added after so that. The first letter of the action and the benefit is lowercased so the sentence reads naturally.
-
Pick how many criteria
Under Acceptance criteria to generate, choose 3 (lean) or 5 (thorough). The default is 3. The story updates as you type or switch.
-
Copy the result
Press the copy button under the generated story to copy the story and all its criteria as plain text, then paste them into your backlog tool and refine them.
Reading the result
- The User story line puts your three phrases into one sentence. With the example values it reads: As a store manager, I want to export a sales report, so that share it with head office.
- With 3 criteria you get Happy path, Invalid or missing input, and Confirmation and persistence. Choosing 5 adds Access control and Empty or edge state.
- Each scenario has a Given (the starting situation), a When (what the user does) and a Then (what the system must do). The Then lines are generic on purpose and need your specific numbers, messages or limits.
- The note under the result says Showing an example while all three fields are empty, and switches to a reminder to refine each Then once you type.
Tips and common mistakes
- Write the benefit so it reads after so that, for example so that they can share it with head office. The tool adds only the words so that.
- The sentence always starts As a, so a role that starts with a vowel, such as admin, comes out as As a admin. Fix the article after you copy.
- Start the action with a common verb such as export, create, add, send, update or approve. The persistence scenario turns these into past tense, like has just exported; other verbs stay as typed.
- If one action needs more than five scenarios to describe, it is probably several stories. Split it and run the tool once per story.
- Replace each Then with something you can test, such as a message text, a time limit or a count, before the story goes to a developer.
Privacy and limits
The story is assembled by a script in your browser. Nothing you type is sent anywhere or saved, and the fields are empty again when you reload the page.
How it works
A good user story captures a requirement from the user's point of view in one sentence, so the whole team knows who wants something and why. This generator follows the standard agile template and pairs it with acceptance criteria written in Gherkin's Given / When / Then style, the format most Agile and BDD teams use because it reads like plain English yet maps cleanly onto automated tests.
You give it three things: the role (the type of user, like “store manager”), the action (what they want to do), and the benefit (the reason it matters). It assembles the story sentence and then generates a set of scenarios, the happy path, invalid input, persistence, access control and empty states, each as a testable Given / When / Then. Choose 3 criteria for a lean story or 5 for a more thorough one.
Treat the output as a strong first draft. Refine each Then into a specific, measurable outcome (a number, a message, a time limit) so it becomes genuinely testable rather than aspirational, that's the difference between a story a developer can build with confidence and one that bounces back in review.
As a [role], I want to [action], so that [benefit].
Given [context], When [action], Then [observable outcome].
Once your stories are scoped, see what building them actually costs with the software development cost calculator, or weigh building against off-the-shelf with the build vs buy calculator. Browse the rest of our free tools for software buyers.
