deliver-acceptance-criteria

Convert user stories into Gherkin-style Given/When/Then acceptance criteria.

Updated May 20, 2026
One-click install
npx skills add https://github.com/richardnguyen0715/ai-chatting-app --skill deliver-acceptance-criteria
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deliver-acceptance-criteria
Source: https://github.com/richardnguyen0715/ai-chatting-app/tree/main/.github/skills/deliver-acceptance-criteria
Command: npx skills add https://github.com/richardnguyen0715/ai-chatting-app --skill deliver-acceptance-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of translating product requirements into well-defined acceptance criteria that are clear and testable for both developers and QA teams.

Core Features & Use Cases

  • Generate Structured Acceptance Criteria: Convert user stories and features into Gherkin-style Given/When/Then scenarios.
  • Support for Different Frameworks: Compatible with popular frameworks like triple-diamond, lean-startup, and design-thinking.
  • Non-Functional Expectations: Capable of addressing performance, security, and reliability expectations.
  • Quick Setup: No setup required; use it immediately after defining a feature or user story.

Quick Start

Run the deliver-acceptance-criteria skill with the user story: 'As a user, I want to be able to order items online, so that I can buy things conveniently.'

Frequently Asked Questions about deliver-acceptance-criteria

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

FAQPage Schema
How do I write testable acceptance criteria for a user story?

Testable acceptance criteria are generated by transforming product requirements into structured Gherkin-style Given/When/Then scenarios. This approach clarifies user stories and defines explicit testing conditions for feature development and QA teams.

What is the best way to convert product requirements into Gherkin format?

Converting product requirements into Gherkin format is best handled by applying predefined templates to structure features into Given/When/Then scenarios. This ensures conditions are clear and testable for developers and QA teams.

Can I include non-functional requirements like performance and security in acceptance criteria?

Yes, non-functional requirements for performance, security, and reliability can be explicitly addressed within acceptance criteria. This ensures feature development meets comprehensive testing expectations beyond core user story functionality.

Do I need to set up a testing framework before generating acceptance criteria?

No testing framework setup is required before generating acceptance criteria. You can immediately use predefined templates to process user stories and output structured Gherkin scenarios for QA teams without environment configuration.

Does this approach support lean-startup and design-thinking frameworks?

Yes, acceptance criteria generation supports multiple product management frameworks including lean-startup, design-thinking, and triple-diamond. This compatibility ensures structured testing conditions align with diverse feature development methodologies.