Free Agile Tool

User Story Generator

Create well-formatted user stories with Given/When/Then acceptance criteria in seconds. No AI, no signup — just structured agile templates.

Build Your User Story

Fill in the three parts of the user story formula.

As a… *

I want to… *

So that… *

Story Size

M — 3–5 points

How to Write Good User Stories

Follow the INVEST Criteria

Good stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable. If a story fails any of these, consider breaking it down further.

Keep It User-Centred

Focus on the "who" and "why" — not just the "what". The role and benefit sections are what separate a great user story from a plain task description.

Write Testable Acceptance Criteria

Given/When/Then format makes criteria precise and easy to verify. Every criterion should be binary — either it passes or it doesn't.

Size Stories Consistently

Use relative sizing (XS–XL) during backlog refinement. Stories sized XL or larger are usually epics and should be split before sprint planning.

Frequently Asked Questions

What is the standard user story format?

The standard format is: "As a [role], I want [action], so that [benefit]." This format ensures every story captures who needs the feature, what they want to do, and why it matters to them.

What's the difference between user stories and tasks?

User stories describe a desired outcome from the user's perspective. Tasks are the technical steps a team takes to deliver that outcome. User stories live in the product backlog; tasks live in the sprint backlog.

How many acceptance criteria should a story have?

Aim for 3–5 acceptance criteria per story. Too few and the story lacks clarity; too many often signals the story should be split. Each criterion should be independently verifiable by a tester.

Now Estimate Your Stories with Planning Poker

You've written the stories — now get your team to size them. Run a free, real-time planning poker session in seconds. No signup required.

Join a Session

Create a Session