A typical feature file will include:
* Title of the feature (e.g. Payments)
* The user story for the feature
* Bullet pointed acceptance criteria at the top
* Any useful links for the developers (e.g. link to UX repository)
* Gherkin scenarios
That's a great summary. I hadn't seen the acceptance criteria as part of the user story before, that's very smart.