Write a complete agile user story with acceptance criteria in a minute. Fill in the role, goal, and benefit, add Given / When / Then scenarios, and copy it into your backlog.
As a [role], I want to [goal], so that [benefit].
Fill in Given, When, and Then for at least one scenario.
A user story is the smallest unit of work in an agile backlog, written from the point of view of the person who benefits from it. The classic template has three parts: who wants it (as a), what they want (I want to), and why it matters (so that). It deliberately leaves out implementation details so the team can decide the best way to deliver the outcome.
The story alone is not enough to build against. Acceptance criteria turn it into something testable - a short list of conditions that must be true before the story is done. Teams that practice behavior-driven development write them as Given / When / Then scenarios, which map directly to automated tests. Teams that want something lighter use a checklist. This generator supports both, and exports Gherkin scenarios as a .feature file you can drop into Cucumber, SpecFlow, or Behave.
Start with a specific role. "As a user" tells the team nothing; "as a project manager reviewing a late sprint" tells them who to design for. Describe the goal as an outcome rather than a button. State a benefit you would defend in sprint planning - if you cannot, the story may not be worth its place in the backlog. Then add two to five acceptance criteria covering the happy path and at least one edge case. The quality check next to the preview flags the most common gaps as you type.
When the story is ready, paste it into t0ggles. The AI task assistant breaks a story into subtasks, suggests a status and priority, and keeps the acceptance criteria in the task description where the whole team can check them off.
Prefer to write by hand? Copy one of these templates into your backlog tool or doc.
The standard three-part format used by most Scrum teams.
As a [type of user], I want to [do something], so that [I get this benefit]. Acceptance criteria: - [ ] [Criterion 1] - [ ] [Criterion 2] - [ ] [Criterion 3]
Situation-first alternative that focuses on context instead of persona.
When [situation], I want to [motivation], so I can [expected outcome]. Acceptance criteria: - [ ] [Criterion 1] - [ ] [Criterion 2]
Given / When / Then scenarios that map directly to automated tests.
Scenario: [short scenario name] Given [starting context] When [action the user takes] Then [expected outcome] Scenario: [edge case] Given [starting context] When [unexpected action] Then [how the system responds]
Paste your story into t0ggles and let the AI split it into subtasks, assign owners, and track acceptance criteria to done. Try it free - no card required.