Acceptance Criteria

Define testable acceptance criteria for Product validation.

irwebtools Updated 0 repo stars
Product Team describes a request, AI Coding builds and verifies, then a working Preview is reviewed

File contents

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.

irwebtools/Product-Skills commit 57ba22c8e3

Frequently asked questions

npx get-skill add irwebtools/acceptance-criteria