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 working on an e-learning platform that hosts thousands of courses, and the current search functionality is frustrating users. Students can't find the courses they need, leading to decreased engagement and course enrollments. The search system was built quickly in the early days and hasn't kept up with the growing content library.
User feedback indicates major pain points: searches return too many irrelevant results, the system is slow during peak hours, and users can't effectively filter by course difficulty, duration, or topic. The business team has identified search improvement as a key driver for increasing course completion rates and platform retention.
The platform now hosts over 5,000 courses across 200+ categories, with 10,000+ active students performing searches daily. The current system struggles with this scale and needs robust requirements to guide the enhancement work.
Create detailed acceptance criteria for the course search functionality. Your document should include:
Save your work as course-search-criteria.md.
The following files are provided as context. Extract them before beginning.
=============== FILE: inputs/search-analytics.md ===============