Free · No sign-up
Turn what you discussed into sprint-ready user stories
Paste the brief, the call, or the requirements doc. Get clear stories in As a / I want / So that form, each one grouped under the requirement it delivers.
How it works
Paste what needs building
A feature brief, a discovery call, a requirements document, or your own notes. Upload a PDF or Word file, or paste the text straight in.
It finds the actors first
Stories go wrong when everyone is 'the user'. The roles are pulled from who was actually named — the sponsor, the reviewer, the admin — and each story is written for the one it serves.
Get a grouped backlog
Stories arrive under the requirement they deliver, so you can see at a glance which requirement is thin and which is doing too much. Export to CSV for Jira, or save it as a project.
Questions
- How many stories will I get per requirement?
- Usually one. Occasionally two or three, when a requirement genuinely serves different actors or different flows. It deliberately does not shred one coherent behaviour into a dozen fragments to look thorough — a padded backlog is harder to work from, not easier.
- Do I have to write the requirements first?
- No. It reads whatever you paste, works out the underlying requirements itself, and shows them alongside the stories so you can see what it understood before you trust the output.
- Can I get acceptance criteria too?
- Yes — the acceptance criteria generator takes the same input and writes Given / When / Then criteria under each story. If you save this into a project instead, you can generate criteria per story and they stay attached to it.
- Will it invent estimates, dates, or numbers?
- No. It carries through figures your source states and leaves out anything it would have to guess. An invented sprint estimate in a story is worse than no estimate, because someone will plan against it.
- Is it free, and do I need an account?
- Free, with no account. You only sign up if you want to save the stories into a project, where they stay connected to their requirements and to whatever you generate next.
What comes next
- Acceptance Criteria GeneratorDefine done for each story in Given / When / Then form.
- RTM GeneratorTrace every requirement down to the stories and tests that cover it.
Or save any of it into a project, where all of this connects up on its own — see every tool.