Acceptance Criteria Generator

Pro v1.0.0 1 view

Generate comprehensive Gherkin-formatted acceptance criteria for user stories with happy path, error states, edge cases, validations, loading states, permissions, and non-functional requirements.

What You Get

Transform 2-3 sentence feature descriptions into complete, developer-ready acceptance criteria in 30 seconds, saving 30-60 minutes per user story.

The Problem

Product managers spend 30-60 minutes manually writing acceptance criteria for each user story, often missing edge cases, error states, and non-functional requirements. Incomplete AC leads to developer questions, rework, and missed edge cases in production.

The Solution

Parse feature descriptions to extract the core capability, user persona, and business context. Generate comprehensive user stories and systematically create 15-30 Gherkin scenarios covering happy path, validations, error handling, edge cases, loading states, permissions, and concurrency concerns. Include non-functional requirements (performance, security, accessibility) and a Definition of Done checklist ready for Jira, Linear, or Shortcut.

How It Works

  1. 1 Parse feature description to extract core capability, user persona, and business context
  2. 2 Generate formatted user story (As a/I want/So that)
  3. 3 Create happy path scenario with Given/When/Then format
  4. 4 Generate validation scenarios (required fields, formats, limits, business rules)
  5. 5 Generate error and edge case scenarios (server errors, network issues, empty states, boundaries)
  6. 6 Generate concurrency scenarios if applicable (conflicts, race conditions, locking)
  7. 7 Generate loading/progress state scenarios for async operations
  8. 8 Generate permission and access scenarios for multi-user contexts
  9. 9 Add non-functional requirements (performance, security, accessibility, browser compatibility)
  10. 10 Format output with Definition of Done checklist and technical notes

What You'll Need

  • Feature description (2-3 sentences minimum)
  • Optional: User persona or role context
  • Optional: Technical constraints or integration points