Write clear, testable acceptance criteria for user stories and feature delivery; use when defining done conditions, creating measurable requirements, applying INVEST checks, documenting negative scenarios, and aligning product, engineering, and QA on expected outcomes.
Does it follow best practices?
Evaluation — 91%
↑ 1.17xAgent success when using this tile
Validation for skill structure
Scenario: [name]
Given [context]
When [action]
Then [outcome]
And [additional outcome]Acceptance Criteria (Must Have):
- [ ] [measurable outcome]
- [ ] [measurable outcome]
Negative/Edge Scenarios:
- [ ] [failure handling]
- [ ] [boundary condition]
Out of Scope:
- [item]