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
- Write criteria Product can demonstrate without reading code.
- Include happy path and important failure cases.
- Align criteria with validation and verification skills.
- 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.