writing-effective-acceptance-criteria

Generates testable acceptance criteria for milestones and user stories.

Updated Aug 27, 2026

Search Tags:#testing #quality #milestones #criteria #product-management #user-stories #acceptance

Ready to run

npx skills add https://github.com/cyarie/cyarie-claude-plugin --skill writing-effective-acceptance-criteria

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-effective-acceptance-criteria
Source: https://github.com/cyarie/cyarie-claude-plugin/tree/main/skills/writing-effective-acceptance-criteria
Command: npx skills add https://github.com/cyarie/cyarie-claude-plugin --skill writing-effective-acceptance-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Acceptance criteria help teams articulate observable outcomes so milestones and user stories can be verified, reducing ambiguity and rework.

Core Features & Use Cases

Enforces testability: each criterion is observable and verifiable.
Guides formatting and grain: favors checklist, Given/When/Then, rules-based, or quantitative formats depending on the scenario.
Scope management: recommends keeping a milestone to a practical number of criteria (e.g., up to five) and provides strategies to split or reframe when needed.
Use Case: product teams drafting milestones for a new feature should produce precise AC that stakeholders can validate in demos and tests.

Quick Start

Draft a concise, testable set of acceptance criteria for a milestone following the 5-AC guideline.

Frequently Asked Questions about writing-effective-acceptance-criteria

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

FAQPage Schema

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

To write testable acceptance criteria, ensure each criterion is observable and verifiable by stakeholders. Use structured formats like Given/When/Then, checklists, rules-based, or quantitative formats to clearly define milestone outcomes and reduce ambiguity during QA reviews.

What is the best format for acceptance criteria in product management?▼

The best format for acceptance criteria depends on the scenario: use checklists for simple validations, Given/When/Then for behavior-driven tests, rules-based for logic constraints, or quantitative formats for measurable milestones. Each ensures scoped granularity and verifiable outcomes.

How many acceptance criteria should a milestone have?▼

A milestone should ideally have up to five acceptance criteria to maintain practical scope. If you exceed this limit, apply strategies to split or reframe the milestone, ensuring the criteria remain scoped, granular, and easily verifiable during product demos and testing.

Why do my acceptance criteria fail during QA testing?▼

Acceptance criteria often fail QA testing when they lack testability, observable outcomes, or scoped granularity. Enforce verifiable formats like Given/When/Then or quantitative rules during milestone definition to reduce ambiguity and prevent rework in product-management workflows.

Can I use Given/When/Then for milestone definitions instead of user stories?▼

Yes, you can use Given/When/Then for milestone definitions. While commonly applied to user stories, this behavior-driven format enforces testability and observable outcomes, making it effective for structuring verifiable criteria in broader product-management planning and QA reviews.