skills.rest
Danhvb
DanhvbCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Acceptance Criteria

Write acceptance criteria in Given-When-Then, checklist, and scenario formats.

Updated Feb 9, 2026
Search Tags:#testability#agile#bdd#checklists#gherkin#user-stories#acceptance-criteria
One-click install
npx skills add https://github.com/Danhvb/my-ba-skills --skill acceptance-criteria-danhvb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Acceptance Criteria
Source: https://github.com/Danhvb/my-ba-skills/tree/main/multi-agent-ba/.agent/skills/senior-ba/acceptance-criteria
Command: npx skills add https://github.com/Danhvb/my-ba-skills --skill acceptance-criteria-danhvb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing precise acceptance criteria is often vague and leads to scope creep. This skill provides structured formats (Given-When-Then, checklists, and scenario-based styles) to ensure all stakeholders share a common, testable definition of done.

Core Features & Use Cases

  • Gherkin-style acceptance criteria using Given-When-Then scenarios for automation and traceability.
  • Checklist format for itemized, testable criteria that can be directly translated into test cases.
  • Scenario-based templates to capture happy paths, edge cases, and error handling across user stories and requirements.
  • Best practices and patterns to improve testability, coverage, and alignment with Definition of Done.

Quick Start

Copy a user story and convert it into a precise Given-When-Then scenario plus a checklist of criteria.

Frequently Asked Questions about Acceptance Criteria

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

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

Testable acceptance criteria for agile user stories are written using structured formats like Given-When-Then, checklists, and scenario templates to ensure all stakeholders share a clear definition of done.

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

The Given-When-Then format is a Gherkin-style scenario structure that defines initial context, user action, and expected outcome to improve testability, automation traceability, and QA coverage.

How do I convert a user story into Gherkin scenarios and checklists?▼

You can convert a user story by generating Gherkin-like scenarios alongside an itemized checklist of criteria, capturing happy paths, edge cases, and error handling for direct QA translation.

Does writing acceptance criteria as checklists help with Definition of Done?▼

Checklist format acceptance criteria directly supports the Definition of Done by providing itemized, testable conditions that can be immediately translated into UAT and QA test cases.

When should I use scenario-based templates instead of checklists for requirements?▼

Scenario-based templates are best when you need to capture complex user story interactions across happy paths and edge cases, whereas checklists suit simple, itemized requirement verification.

Related Skills

Explore More Product & Management Skills→
KentoShimizuKentoShimizu
7

user-story-writing

Convert prioritized requirements into sprint-ready user stories with acceptance criteria.

Community
Advanced
michsindlingermichsindlinger
1

acceptance-testing

Define acceptance criteria and manage User Acceptance Testing workflows.

Community
Advanced
devCharuzudevCharuzu

agile-product-owner

Organize Agile backlog management and sprint execution with user stories and capacity planning.

Community
Advanced
shafibabarshafibabar
1

acceptance-criteria

Generate and validate structured acceptance criteria using Gherkin and rule-based formats.

Community
Advanced