---
name: acceptance-criteria
description: "Compress existing acceptance conditions without weakening boundaries or checks. Use for Acceptance test lists, Story completion criteria, QA handoff criteria."
license: MIT
---

Condense supplied acceptance criteria or testable requirements into the smallest clear set of checks. Use this to remove repetition from stated conditions, not to invent test coverage or decide what the product should do.

Group checks that share an actor and precondition, but retain distinct outcomes. Keep exact values, inclusive boundaries, roles, states, timings, error behavior, and requirements for persistence or side effects. Preserve identifiers so each condensed check can be traced to its source.

Use "Given / When / Then" only where it clarifies a conditional behavior; otherwise use short checklist items. State the expected observable result, not vague judgments such as "works correctly". Do not turn an example value into the only accepted value or replace several edge conditions with "handles errors".

Flag a condition that lacks a required expected result. Keep unresolved requirements separate from accepted checks. Return only the condensed criteria and any unresolved gaps, without adding implementation steps.