User Story Generator
Describe a feature or epic. Get the stories, the acceptance criteria and the edge cases your team would otherwise find in testing.
How it works
Describe the feature
One epic per run: what it does, who is involved. Name the personas if you have them.
Get stories with criteria
As a / I want / so that, a priority, and two to four Given/When/Then criteria per story — testable by a person, not just a developer.
Edge cases included
Empty states, invalid input, conflicting actions, permission boundaries and notifications, not only the happy path.
Why acceptance criteria matter more than the story
The story says what. The criteria say when it is done.
Testable by anyone
Given/When/Then reads as a test a product owner can run by clicking. That is the whole point.
Permissions, written down
"A manager cannot approve their own request" is a story nobody writes and everybody needs.
The notifications nobody asked for
Who is told what, when — the criteria most features ship without.
Questions about user stories
-
What format are the stories in?
The classic "As a [persona], I want [capability], so that [outcome]", with a must/should/could priority and Given/When/Then acceptance criteria. Copy them, download them as Markdown, or share the link.
- How many stories will I get?
- Can I paste a PRD?
- Is it really free?
- What happens to what I type?
- Can I use the result outside Chattee?
From backlog to working feature
Chattee implements the stories — screens, rules, permissions — as part of a full-stack app. Planning is free.