acceptance-criteria

Create and maintain acceptance criteria using Given/When/Then format.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/a53ali/ai-dev --skill acceptance-criteria-a53ali
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acceptance-criteria
Source: https://github.com/a53ali/ai-dev/tree/main/skills/qa/acceptance-criteria
Command: npx skills add https://github.com/a53ali/ai-dev --skill acceptance-criteria-a53ali

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users write clear, testable acceptance criteria for user stories, reducing ambiguity and improving collaboration between developers and QAs.

Core Features & Use Cases

  • Given/When/Then Format: Provides a structured format for writing acceptance criteria.
  • Definition of Ready (DoR) and Definition of Done (DoD): Offers guidelines to ensure stories are ready for development and complete upon delivery.
  • Non-Functional Requirements (NFR) Handling: Assists in writing scenarios for performance, security, and accessibility.
  • Jira MCP Integration: Integrates with Jira to update stories with acceptance criteria and search for missing AC.

Quick Start

Use the acceptance-criteria skill to write acceptance criteria for your user story.

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 using Given/When/Then format?

Acceptance criteria using Given/When/Then format are written by defining the initial context with Given, the action with When, and the expected outcome with Then. This structured Gherkin approach ensures scenarios are testable and reduces ambiguity for developers and QAs.

What is the best way to manage Definition of Ready and Definition of Done for user stories?

Managing Definition of Ready and Definition of Done involves checking user stories against predefined guidelines before development and upon delivery. Applying these definitions ensures stories are fully prepared and meet quality standards before closing.

Can I automatically update Jira user stories with acceptance criteria?

Yes, you can automatically update Jira user stories with acceptance criteria through Jira MCP integration. This feature searches for stories missing acceptance criteria and pushes structured Given/When/Then scenarios directly to the issues.

How do you write acceptance criteria for non-functional requirements?

Writing acceptance criteria for non-functional requirements involves creating specific Given/When/Then scenarios for performance, security, and accessibility. This ensures NFRs are explicitly defined, testable, and integrated into the user story workflow.

Does formatting acceptance criteria with Gherkin improve collaboration between developers and QAs?

Formatting acceptance criteria with Gherkin improves collaboration between developers and QAs by providing a shared, structured Given/When/Then syntax. This clarity reduces ambiguity in user stories and aligns expectations for testable outcomes.