One way is to write (BDD) feature files for the story

User stories are an improved form of the traditional ‘FRS / SRS’

And sometimes the ambiguity we saw with traditional requirements can be felt in stories as well

Feature files explaining how the implementation should work is a great way of clarifying

It makes the ‘subjective’ nature of the story to a more ‘absolute’ expected behavior

And you can link your gherkin files to your user story

More on that here