Free AI Tool
Acceptance Criteria Generator
Paste a user story and get complete acceptance criteria in Gherkin (Given/When/Then) format, covering happy path, edge cases, and error states.
Fill in the form and click generate to see your AI-powered results
How it works
Write or paste your user story in the standard "As a... I want... so that..." format
Claude generates 3–4 acceptance criteria scenarios covering happy path, edge cases, and errors
Paste the criteria directly into your ticket before bringing it to planning poker
Frequently asked questions
Related tool
styleOpen Planning PokerAll free tools
Browse all tools →Learn more
What is acceptance criteria? →What are acceptance criteria in agile?expand_more
Acceptance criteria define the conditions a user story must meet to be considered complete from the product owner's perspective. They set clear expectations before development starts.
What is Gherkin format for acceptance criteria?expand_more
Gherkin uses "Given / When / Then" syntax to describe behavior: Given a context, When an action occurs, Then an outcome should happen. It's human-readable and can be used directly in BDD test frameworks.
How many acceptance criteria should a user story have?expand_more
Most stories need 3–5 criteria: one for the main happy path, one or two for edge cases, and one for the primary error state. More than 5 often means the story is too large and should be split.
When should I write acceptance criteria?expand_more
Before refinement or planning poker. Criteria should exist before the team estimates a story, so everyone understands the scope. Stories without criteria are consistently over- or under-estimated.
Estimate stories with acceptance criteria in planning poker
Free to start. No credit card required.