User stories are an industry standard way to express the requirements of different user groups. Wherever possible, write stories that target a single persona. User stories follow this formula: As a __(user persona)__ I want to __(perform some action)__ so that __(outcome or rationale)__.
This is simply the user persona segment that the story describes
Keep actions short and to the point. When exported, into PM software, these will be the "summary" line and so should stand alone to orient a reader to the core of the functionality.
This is where the "why" of the feature or functionality can begin to be expressed. It may be necessary to express practical outcomes, but often these are better listed as Acceptance Criteria
Acceptance Criteria (a/c for short) express the minutiae of a feature and can become quite granular. The more complex a story is, the greater its need for some detailed a/c to ensure clarity and common understanding.
Userforge provides several "Additional Info" sidebar options to enrich stories. These make space for research insights and production notes that add relevant context without cluttering the core story.
The beautiful clarity of user stories written in Userforge extends to our Jira Software integration as well:
Changes made in Userforge are updated and logged to Jira history tab
Comments made in Jira are visible in Userforge (maintains a single source of truth)
On some plans, story status and estimates are also visible in Userforge