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
Given/When/Then:
Scenario: Successful checkout
Given a user has items in cart
When the user submits payment with valid details
Then an order confirmation page is displayed
And a confirmation email is sent within 5 secondsRule-oriented: