Acceptance Criteria

You might say

Write clear acceptance criteria for the itinerary feature: saving shows the trip, refresh keeps it, and invalid dates explain how to fix them.

Acceptance criteria are checkable conditions that determine whether a result is acceptable.For an itinerary, saving can show the trip, refresh can keep it, and an end date before the start date can explain how to correct it. This turns “mostly done” into observable results. Code coverage or framework choice alone cannot prove the user need is complete.

Know first

PRD

Acceptance Criteria

How an itinerary request becomes checkable completion

trip.local/hangzhou-weekendDraft

Hangzhou · Weekend for two¥1,240

09:30West Lake40 min walk

14:00Zhejiang Art MuseumRain plan · indoors

!End date cannot be before start date

Every item on the left must have evidence in the real page on the right.

What evidence acceptance needs

State a result a person can see: “Show an itinerary card after save,” “keep it after refresh,” and “explain an invalid date” can all be checked in the page. “Good experience” and “works normally” cannot.

Align scope before building: Ask an AI Agent to implement against the conditions, then operate and record each result. The same completion basis works for features, fixes, and handoff.

Quick checkChoose the best answer

The team says the itinerary feature is done but nobody has operated the page. Which is the best acceptance criterion?

Saving a valid itinerary shows its card, it remains after refresh, and invalid dates explain how to fix themUse the latest framework, reach 80% coverage, and keep files tidyThe page looks professional and everyone feels it can ship

You can say this to an AI Agent

Implement itinerary saving against these three acceptance criteria: show an itinerary card after save, keep it after refresh, and tell people how to fix invalid dates. Then operate each case and report the result for every criterion.

Learn next

1Test Case→2End-to-End Test→