In Behavior-driven development approach(90% of user stories out there) make sure you have below content in the story. Notes: - write only functional/business (WHAT part) requirements in the story - leave technical implementation(HOW part) to developers tasking during planning or pre-planning sessions. Story: ROLE: As a GOAL: I need to REASON: So that I can . Acceptance Criteria: - functional requirements 1-n. Gherkins:( high-level test case) GIVEN: I need WHEN: I<div>THEN: I should see Note: write as many gherkins as needed to cover highlevel test cases.</div>