A feature request can state what someone wants while leaving the conditions for success unresolved. Acceptance criteria make those conditions verifiable. They turn a user story’s purpose into expected behavior that people can discuss before implementation and check afterward. section 1.2
Password reset must revoke existing access
“Reset my password” does not settle what happens to sessions already open on other devices. A criterion makes the missing decision explicit: after a successful reset, invalidate every existing session and require a new login. Other scenarios distinguish a reset link opened within 30 minutes from one opened after it expires. A test can then create sessions on several devices, complete the reset, and assert that no active sessions remain. section 1.2
Listing 1.2 Acceptance criteria password reset user story
Scenario: Resetting a password revokes existing access Given I am an account holder with one or more active sessions And I have requested a password reset When I successfully set a new password using the reset link Then all existing sessions for my account are invalidated And I must log in again on any device Scenario: A reset link is valid only for a limited time Given I have requested a password reset When I open the reset link within 30 minutes Then I am allowed to choose a new password Scenario: An expired reset link cannot be used Given I have requested a password reset When I open the reset link after 30 minutes Then the link is rejected And I am prompted to request a new one
The password-reset scenarios show how preconditions, actions, and observable results expose decisions that a short feature request could miss. section 1.2
In spec-driven development, acceptance criteria belong in the discovery conversation about purpose and scope, before technical design or execution tasks. For an anonymous URL shortener, criteria can require a unique short URL for valid input and a client error with no stored mapping for invalid input. The specification records these decisions; design choices and task checklists follow from them. section 2.2.1 section 2.4.4
Treat criteria as the result of dialogue, not a document handed over or generated from an unexamined one-line prompt. Keep enough detail to prevent critical assumptions, then review the scenarios against the intended outcome. A weak check that merely finds some result is less useful than one that verifies the exact expected result. section 2.1.2








