acceptance-criteria

Convert requirements into measurable acceptance criteria in YAML.

2|Updated Oct 19, 2025

Search Tags:#requirements #QA #acceptance-criteria #SMART #given_when_then #test-criteria

Ready to run

npx skills add https://github.com/masanao-ohba/claude-manifests --skill acceptance-criteria

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acceptance-criteria
Source: https://github.com/masanao-ohba/claude-manifests/tree/main/skills/generic/acceptance-criteria
Command: npx skills add https://github.com/masanao-ohba/claude-manifests --skill acceptance-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts requirements into measurable acceptance criteria that can be objectively evaluated during delivery.

Core Features & Use Cases

GWT (Given-When-Then) format to express preconditions, actions, and outcomes for each criterion.
SMART criteria to ensure specificity, measurability, achievability, relevance, and time-bound evaluation.
Automation-ready output: publishes clean YAML blocks for integration with test plans, QA checks, and traceability.

Quick Start

Provide user stories or project requirements to generate a full acceptance-criteria document. The skill will output structured criteria including functional, non-functional, and quality sections ready for review and automation.

Frequently Asked Questions about acceptance-criteria

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

FAQPage Schema

How do I write measurable acceptance criteria from user stories?▼

Acceptance criteria are testable conditions that a software feature must satisfy. They are defined by transforming user stories into functional, non-functional, and quality criteria using SMART and Given-When-Then formats to verify delivery success.

What is the best way to format acceptance criteria for QA automation?▼

The best way to format acceptance criteria for QA automation is to output structured YAML blocks. This provides clean, machine-readable definitions for functional, non-functional, and quality criteria that integrate directly with test plans and traceability.

How do I use Given-When-Then to make test criteria objective?▼

Given-When-Then structures test criteria by defining preconditions (Given), user actions (When), and expected outcomes (Then). This format ensures acceptance criteria are objectively verifiable during the software delivery and QA workflow.

Can I generate both functional and non-functional requirements from specs?▼

Yes, you can generate both functional and non-functional requirements from specs. The process transforms project specifications into a structured document that separates functional, non-functional, and quality criteria with defined priorities and verification methods.

Do I need SMART goals to define testable software requirements?▼

You need SMART criteria to define testable software requirements because they ensure specificity, measurability, achievability, relevance, and time-bound evaluation. This prevents ambiguous criteria and makes QA validation objective during delivery.