acceptance-criteria-definer

Define testable acceptance criteria for user stories in Given-When-Then format.

1|Updated Jan 22, 2026

Search Tags:#testing #requirements #qa #acceptance criteria #user stories #given when then

Ready to run

npx skills add https://github.com/Ethical-AI-Syndicate/skills --skill acceptance-criteria-definer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acceptance-criteria-definer
Source: https://github.com/Ethical-AI-Syndicate/skills/tree/main/acceptance-criteria-definer
Command: npx skills add https://github.com/Ethical-AI-Syndicate/skills --skill acceptance-criteria-definer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps ensure shared understanding and testability by defining clear, actionable acceptance criteria for user stories, preventing ambiguity and scope creep.

Core Features & Use Cases

Structured Scenario Generation: Produces Given-When-Then scenarios for happy paths, alternate paths, and error handling.
Edge Case Identification: Guides the identification of boundary conditions and potential failure points.
Validation Approach: Defines how criteria will be validated (automated vs. manual).
Use Case: After drafting a user story for a new login feature, use this Skill to generate specific acceptance criteria like "Given a user with valid credentials, When they enter their username and password and click 'Login', Then they are redirected to their dashboard."

Quick Start

Use the acceptance-criteria-definer skill to generate acceptance criteria for the user story "As a user, I want to reset my password so that I can regain access to my account."

Frequently Asked Questions about acceptance-criteria-definer

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

FAQPage Schema

How do I write testable acceptance criteria for user stories?▼

To write testable acceptance criteria, use a structured Given-When-Then format to specify scenarios, edge cases, and validation approaches. This ensures shared understanding and prevents ambiguity by covering happy paths, alternate paths, and error handling.

What is the Given-When-Then format for acceptance criteria?▼

The Given-When-Then format structures acceptance criteria by defining a precondition (Given), an action (When), and an expected outcome (Then). It generates testable scenarios for software development, addressing both standard paths and boundary conditions.

How do I identify edge cases and boundary conditions for QA testing?▼

Identify edge cases by defining acceptance criteria that explicitly address potential failure points and boundary conditions. Structuring scenarios using Given-When-Then guides the identification of alternate paths and error handling for comprehensive QA validation.

What is the best way to define validation approaches for software requirements?▼

The best way to define validation approaches is to specify whether criteria will be validated automatically or manually during scenario generation. This approach ensures testability and prevents scope creep by clearly defining validation methods for each user story.

Can I generate acceptance criteria to prevent scope creep in product management?▼

Generating structured acceptance criteria prevents scope creep by ensuring shared understanding and testability. Defining actionable Given-When-Then scenarios clarifies boundaries and expected outcomes for user stories before development begins.

Does the acceptance-criteria-definer output structured data for user stories?▼

The acceptance-criteria-definer outputs structured data by adhering to a YAML schema for output consistency. It generates Given-When-Then scenarios, edge cases, and validation approaches to ensure actionable and testable user story requirements.