We can discuss requirements before committing to work.
The feature will be described from under perspective in the form of user stories.
User Story Temaplte:
As <role> I want to <goal> so that <benefit> .
For communicating clear requirements to the developer and QA the Acceptance Criteria will be Written in Gherkin Format:
Given, When, Then
For quick understanding, User flows will also be included.