Turn a rough feature idea into clear, testable acceptance criteria — Given / When / Then, non-functional requirements, and the edge cases most teams forget. Written the way a disciplined Product Owner would.
Acceptance Criteria Generator
Live · Claude API
Describe what you want to build in plain language. A sentence or a paragraph — the messier the better, that's what this is for.
Paste titles + one-line summaries of stories or epics already in your backlog. If this looks like a duplicate, we'll flag it — nothing gets merged or blocked automatically, you make the call.
Writing a Feature from an Epic, or a Story from a Feature? Paste the parent level here so the new output stays consistent with what it already establishes — this doesn't get checked or enforced, just used to inform the writing.
Pasting straight into your work tool? Pick its format and the output will match how it expects a story and criteria to be structured.
A real feature is usually many stories, not one. This generates a first slice — 2-3 distinct stories — not the full breakdown. Multiple-story mode trims NFRs and edge cases per story to fit the same generation budget as a single story.
Structured as a user story with Given/When/Then acceptance criteria.
This generates 2-3 stories as a first phase — a full 10-12 story breakdown is a planned future release, not what this does yet.
Thinking through the scenarios
Generated Acceptance Criteria
Preview
This is a plain text file — not a direct import into Jira or Azure DevOps.
Built with the Anthropic Claude API — a working tool, not a mockup.