Free tool
Paste a story and its acceptance criteria. Seven checks run as you type: who it is for, what they want, why, whether it is one story, whether the words can be tested, and whether the criteria cover what happens when something goes wrong.
Runs in your browser. Nothing you type leaves this page.
Result
2 of 7 checks pass
Who it is for Worth a look
“user” is generic. Name the kind of person, such as a returning buyer or a finance approver, so the team knows what they know and need.
What they want Passes
The story says what the role wants to do.
Why Fix
Add the reason: “so that …”. Without it, nobody can suggest a smaller way to meet the same need.
One story Worth a look
The want joins two things with “and”. If each could ship on its own, make them two stories.
Words you can test Fix
“fast”: say how fast, such as “within 2 seconds”. “quickly”: say how fast, such as “within 2 seconds”. “easy”: say what the user can do, and in how many steps.
Acceptance criteria Passes
2 criteria.
When something goes wrong Fix
No criterion says what happens when something goes wrong. Add one for an error, an empty state or invalid input.
Also consider
These checks read how a story is written, not whether it is the right story. In SyncupHUB the PO Agent reviews requests with your product’s context, for a product owner to approve.
Check 1
Who it is for
A named role, not “a user”, so the team knows whose problem it is.
Check 2
What they want
One thing the role can do, in their words.
Check 3
Why
The outcome behind the want, so a smaller solution can be considered.
Check 4
One story
Small enough to finish in a sprint, with one want rather than two joined by “and”.
Check 5
Words you can test
No “fast”, “easy” or “intuitive” without a number or a step count.
Check 6
Acceptance criteria
Usually three to six, each one checkable by a tester.
Check 7
When something goes wrong
At least one criterion for an error, an empty state or invalid input.
Starting from scratch? Copy the user story template.
A good user story names a specific role, the one thing that role wants to do, and the reason, in plain words. It is small enough to finish in a sprint, and its acceptance criteria say how anyone will know it is done, including what happens when something goes wrong.
The story says who wants what, and why. The acceptance criteria are the conditions the work must meet to count as done, written so a tester can check each one. A story without criteria can be argued about; criteria turn it into something you can test.
No. It applies fixed rules in your browser, and nothing you type is sent anywhere. It catches common problems in how a story is written, not whether it is the right story. In SyncupHUB, the PO Agent reviews requests with your product’s context, for a product owner to approve.
SyncupHUB checks requests as they arrive, reads status and risk from the work, and keeps the evidence for every release, with AI that proposes and people who approve. Cloud is free for the first month.