Acceptance Criteria Generation

Name: Acceptance Criteria Generation
Availability: InStock
Author: Kolb

Generate structured acceptance criteria from user stories in Agile software projects.

Updated Aug 27, 2026

Search Tags:#templates #agile #quality #acceptance-criteria #given-when-then #test-cases #criteria-generation

Ready to run

npx skills add https://github.com/mkolb22/zen-plugin --skill acceptance-criteria-generation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Acceptance Criteria Generation
Source: https://github.com/mkolb22/zen-plugin/tree/main/skills/acceptance-criteria-generation
Command: npx skills add https://github.com/mkolb22/zen-plugin --skill acceptance-criteria-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating precise and testable acceptance criteria from user stories can be time-consuming and error-prone. This skill codifies a repeatable approach, ensuring requirements are explicit, verifiable, and aligned with stakeholder intent.

Core Features & Use Cases

Supports Given-When-Then style criteria, edge cases, and non-functional considerations.
Produces a structured output with story_reference, story_title, functional_criteria, non_functional_criteria, and test_mapping, ready for downstream QA and test automation.
Includes templates and guidance for domain-specific scenarios (authentication, form submissions, data listing, file uploads) to accelerate working with Agile teams.

Quick Start

Provide a user story and expected benefit, and the skill will generate structured acceptance criteria.

Frequently Asked Questions about Acceptance Criteria Generation

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

FAQPage Schema

How do I generate testable acceptance criteria from an Agile user story?▼

Generating acceptance criteria from a user story requires providing the story and expected benefit to produce structured, testable requirements. The output maps functional and non-functional constraints using Given-When-Then style for downstream QA validation.

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

Given-When-Then format structures acceptance criteria by defining a starting context, an action, and the expected result. This ensures user stories are explicit, verifiable, and aligned with stakeholder intent for Agile QA validation.

How do I include non-functional requirements in Agile acceptance criteria?▼

Including non-functional requirements in acceptance criteria involves generating a structured output that separates functional and non-functional constraints. This ensures quality attributes are covered alongside standard Given-When-Then test cases.

Can I use acceptance criteria generation for domain-specific scenarios like file uploads and authentication?▼

Acceptance criteria generation supports domain-specific scenarios like file uploads, authentication, and form submissions. It applies specialized templates to these contexts to accelerate requirement refinement in Agile software projects.

How do I map acceptance criteria to test cases for QA validation?▼

Mapping acceptance criteria to test cases involves generating a structured YAML-ready output containing a test_mapping field. This directly links functional criteria and edge cases to downstream test automation and coverage checklists.

What is the best way to write acceptance criteria for edge cases in user stories?▼

Writing acceptance criteria for edge cases requires a repeatable generation approach that applies coverage checklists to user stories. This ensures requirement refinement captures non-functional considerations and domain-specific edge cases explicitly.