Define clear and measurable criteria for the story to be considered complete and successful.
Brief description of the context and reasons why this user story is necessary.
Detailed description of the feature or improvement. Include specific details on what needs to be done.
List the assumptions made during the drafting of this user story.
Identify any constraints, such as technical, resource, or schedule limitations.
Include links to prototypes, mockups, or wireframes associated with this user story.
List any open questions or points that need clarification.
Additional notes: Add any extra information that might be useful for the development and testing teams.