acceptance-criteria-generator

Generate Gherkin Given/When/Then acceptance criteria from user stories.

Updated May 9, 2026

Search Tags:#requirements #acceptance criteria #user stories #bdd #gherkin #scenario outline #qa coverage

Ready to run

npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill acceptance-criteria-generator-gustavogutierrez

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acceptance-criteria-generator
Source: https://github.com/GustavoGutierrez/engineering-skills/tree/main/skills/acceptance-criteria-generator
Command: npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill acceptance-criteria-generator-gustavogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns vague user stories and specifications into precise, testable Behavior-Driven Development (BDD) acceptance criteria that remove ambiguity for both engineering and QA.

Core Features & Use Cases

Gherkin Given/When/Then generation: Produces acceptance criteria in standard Gherkin format for clear pass/fail verification.
Coverage-first scenario planning: Includes happy paths, business-rule validations (boundaries/roles/state transitions), and sad paths (errors/invalid inputs/permission failures).
Clarity through targeted questions: Asks for missing details before guessing when actor, scope boundaries, or error behaviors are unclear.

Quick Start

Ask for acceptance criteria by saying you want Gherkin Given/When/Then scenarios for your user story, including happy path, business-rule edge cases, and sad paths.

Frequently Asked Questions about acceptance-criteria-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write Gherkin acceptance criteria from a vague user story?▼

To write Gherkin acceptance criteria from a vague user story, transform the requirements into Given/When/Then scenarios covering happy paths, sad paths, and edge cases. The Skill requests clarifications on unclear boundaries or actors before generating verifiable pass/fail conditions.

What is the best way to ensure QA coverage for BDD scenarios?▼

The best way to ensure QA coverage for BDD scenarios is generating testable Gherkin Given/When/Then formats that include happy paths, business-rule validations, and sad paths. This approach provides binary pass/fail criteria without tying scenarios to implementation details.

Can I use Scenario Outline with Examples for my acceptance criteria?▼

Yes, you can use Scenario Outline with Examples for your acceptance criteria. The Skill optionally generates Scenario Outlines to handle multiple input variations efficiently, converting rough requirements into structured, reusable testable scenarios for manual or automated execution.

How do you handle vague requirements when creating testable scenarios?▼

When creating testable scenarios from vague requirements, the Skill asks targeted questions to clarify missing details like actor boundaries or error behaviors before guessing. This ensures the final Gherkin Given/When/Then scenarios are precise and verifiable.

Does Gherkin Given/When/Then generation include sad paths and edge cases?▼

Yes, Gherkin Given/When/Then generation includes sad paths and edge cases. The Skill applies coverage-first scenario planning to map business-rule validations, boundary errors, invalid inputs, and permission failures alongside the standard happy path.