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
Your team is building a new e-commerce platform for a mid-sized retail company. The product manager has identified that checkout abandonment is a major issue with their current system - users frequently leave during the payment process due to slow performance and unclear error handling. The company processes about 1,000 transactions per day and needs a robust, user-friendly checkout experience.
The development team has the basic shopping cart functionality complete, but the checkout flow needs to be clearly defined before implementation begins. The system needs to handle various payment methods, provide clear feedback to users, and perform reliably under normal load conditions.
Create a comprehensive acceptance criteria document for the checkout flow feature. The document should include:
Save your work as checkout-acceptance-criteria.md.
The following files are provided as context. Extract them before beginning.
=============== FILE: inputs/current-issues.md ===============