User story generator
Write user stories with acceptance criteria in the As a / I want / so that format.
FreeRuns in your browserNo signupUpdated 2026-11-05
The story below is an example for a booking app. Replace it with your own.
## BOOK-12: See all of today's appointments on one screen **As a** clinic receptionist, **I want** to see all of today's appointments on one screen, **so that** I can spot gaps and fit in walk-in patients. Priority: Must have · Estimate: 3 points ### Acceptance criteria **Scenario 1: Viewing today's list** - **Given** I am signed in as a receptionist - **When** I open the schedule - **Then** I see today's appointments in time order - **And** each one shows the patient, practitioner and status **Scenario 2: Spotting a free slot** - **Given** a practitioner has no booking between 10:00 and 10:30 - **When** I view the schedule - **Then** that time is shown as free - **And** I can start a booking from it **Scenario 3: A patient cancels** - **Given** a patient cancelled their 11:00 appointment - **When** I view the schedule - **Then** the appointment is marked as cancelled - **And** its time is shown as free
Story check
- ✓ Role is specific
- ✓ One goal per story
- ✓ Benefit stated
- ✓ Every scenario has Given, When and Then
- ✓ Small enough to fit in a sprint
A good story describes a need, not a solution. If the acceptance criteria could not be tested by someone outside the team, make them more concrete.
About this tool
How it works and how to read the result.
Need this done for you?
Web app & SaaS development
SaaS products and web apps, from first version to scale.
See the serviceWhat it does
This user story generator turns a role, a goal and a benefit into a properly formatted user story with acceptance criteria. Write criteria as Given, When, Then scenarios or as a simple checklist, add an ID, a priority and a story-point estimate, and the page writes the story as Markdown for GitHub, Jira, Linear or Notion, as plain text, or as a Gherkin feature file for test tools such as Cucumber. A short check flags common problems: a vague role, two goals in one story, a missing benefit or an incomplete scenario. It runs in your browser.
How to use it
- Enter who the story is for, what they want to do and why.
- Choose scenarios or a checklist for the acceptance criteria.
- For scenarios, fill in Given, When and Then. Put extra conditions on new lines and they become "And" steps.
- Add an ID, priority, estimate and any notes, such as a link to the design.
- Pick an output format, then copy or download the story.
How to read the result
The example is a story for a clinic booking app: "As a clinic receptionist, I want to see all of today's appointments on one screen, so that I can spot gaps and fit in walk-in patients." With ID BOOK-12 and no title entered, the heading becomes "BOOK-12: See all of today's appointments on one screen". It is marked Must have with an estimate of 3 points.
It has three scenarios. "Viewing today's list" checks the order and the details shown. "Spotting a free slot" checks that a gap between 10:00 and 10:30 is shown as free and can be booked. "A patient cancels" checks that a cancelled 11:00 appointment is marked and its time freed. Each one is specific enough that a tester who has never seen the design could check it.
All five checks pass for the example. Change the goal to "to see today's appointments and send reminders" and the check warns that the goal contains "and", because reminders are a separate need with their own criteria. Change the role to "user" and it asks for something more specific, since a receptionist and a patient need very different schedules. Pick 13 points and it suggests splitting.
The Gherkin output follows the standard layout: a Feature line, the story as its description, then each Scenario with its steps indented beneath. Save it as a .feature file in your test folder if your team runs behaviour-driven tests.
Once each story has an estimate, plan the release dates with the project timeline calculator. When your backlog is ready to build, our web app development service can take it from there.
Questions
Frequently asked.
What is the user story format?
As a [role], I want [goal], so that [benefit]. The role says who needs the change, the goal says what they want to do, and the benefit says why. The format keeps the focus on a person and a need rather than a technical task, which makes it easier to judge whether the finished work actually helps anyone.
What are acceptance criteria?
The conditions a story must meet to count as done. They are written before the work starts, so the person building it and the person checking it agree on what done means. Given, When, Then scenarios describe a starting situation, an action and the expected result, and can be turned into automated tests.
How big should a user story be?
Small enough to build and test within one sprint, and ideally within a few days. If the goal contains "and", or the acceptance criteria run to more than a handful of scenarios, it is usually two stories. Split by user action or by rule, not by layer: "book an appointment" and "cancel an appointment", not "build the API" and "build the screen".
More in Business & pricing
Related tools.
Your next move
Like what you see? Tell us about it.
A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.
India · Working with clients worldwide