acceptance-criteria-patterns

Automates Given/When/Then acceptance criteria templates for feature specifications.

4|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/AI-Foundry-Core/ril-agents --skill acceptance-criteria-patterns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: acceptance-criteria-patterns
Source: https://github.com/AI-Foundry-Core/ril-agents/tree/main/plugins/product-specification/skills/acceptance-criteria-patterns
Command: npx skills add https://github.com/AI-Foundry-Core/ril-agents --skill acceptance-criteria-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations struggle to define precise, testable criteria for features, leading to scope creep and ambiguous QA. This skill provides proven Given/When/Then patterns, quality gates, and definition-of-done templates to codify expectations.

Core Features & Use Cases

  • Given/When/Then templates to structure acceptance criteria for features and user journeys.
  • Definition of Done templates to standardize completion criteria across teams and pipelines.
  • Quality gate checklists to ensure criteria cover happy paths, edge cases, errors, performance, and accessibility.
  • Guidance for translating vague requirements into verifiable, independent criteria with real-world examples.

Quick Start

Create a set of Given/When/Then acceptance criteria templates for a feature specification.

Frequently Asked Questions about acceptance-criteria-patterns

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

FAQPage Schema
How do I write testable acceptance criteria for feature specifications?▼

To write testable acceptance criteria, use Given/When/Then templates to structure feature specs and user journeys. This translates vague requirements into verifiable, independent criteria that codify expectations for product managers, developers, and QA teams.

What is a definition of done template for standardizing feature completion?▼

A definition of done template standardizes completion criteria across teams and pipelines. It ensures that feature specifications meet consistent quality gates before delivery, preventing scope creep and ambiguous QA outcomes.

How do I translate vague product requirements into verifiable BDD-style criteria?▼

Translate vague product requirements into verifiable criteria by applying BDD-style Given/When/Then patterns. This codifies expectations into independently verifiable criteria with real-world examples covering happy paths, edge cases, and errors.

Can I use quality gate checklists to cover edge cases and accessibility in feature specs?▼

Yes, quality gate checklists ensure acceptance criteria cover happy paths, edge cases, errors, performance, and accessibility. They standardize completion criteria across teams and pipelines to prevent scope creep and ambiguous QA.

Does this approach work for setting quality gates across different development pipelines?▼

Yes, this approach applies to setting quality gates across different pipelines. It provides definition-of-done templates and checklists to standardize completion criteria, ensuring each criterion remains independently verifiable across teams.