# Acceptance Criteria

> Define testable acceptance criteria for Product validation.

- Skill: `irwebtools/acceptance-criteria` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add irwebtools/acceptance-criteria`
- Raw SKILL.md: https://api.skillmd.com/api/skills/irwebtools/acceptance-criteria/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: irwebtools (https://skillmd.com/u/irwebtools)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/irwebtools/acceptance-criteria

---


# acceptance-criteria

## When to use

Use when the task matches: acceptance-criteria, AC, definition of done.

## Purpose

Make success observable for Product review before developer handoff.

## Inputs

- User stories
- Business rules
- Scope boundary

## Process

1. Write criteria Product can demonstrate without reading code.
2. Include happy path and important failure cases.
3. Align criteria with validation and verification skills.
4. Mark deferred criteria explicitly.

## Outputs

- Acceptance criteria per story
- Negative cases
- Demo checklist

## Verification

- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.

## Restrictions

- Do not use vague criteria such as user-friendly.
- Do not treat developer unit tests as Product acceptance.
- Do not add hidden scope through criteria.