Overview
Requirements Style lets you define your organization's preferred requirement format by providing examples. Once configured, Glossa uses those examples to shape the title, body, length, and style of every requirement it generates — so the output matches the way your team is used to using and engaging with requirements.
Requirements Style is a workspace-level setting, so it applies across all projects.
Setting Up Requirements Style
Go to Settings → Requirements Style
Click Add Style Example
Enter a Requirement Title and Requirement Body for your first example
Repeat until you have at least 3 examples
Save your settings
You can add up to 10 examples. The more examples you provide, the more accurately Glossa can match your style.
Note: Requirements Style takes effect on the next file you upload. It does not retroactively update requirements that have already been generated.
Showing or Hiding Requirement Titles
Some teams work primarily from the requirement description and don't want a separate title shown. In Settings → Requirements Style, you can turn requirement titles off for your workspace.
Show requirement titles is checked (default): Each requirement shows its title as the primary label, with the description beneath.
Show requirement titles is unchecked: The requirement description becomes the primary label in both the requirements list and the requirement detail view. Titles are hidden from view.
This is a workspace-level setting, so it applies across all projects. It changes only how requirements are displayed — it does not delete or alter the underlying title text.
What Glossa Learns From Your Examples
Glossa uses your examples to replicate:
Format — how the title and body are structured
Style — the voice and phrasing you use (e.g., "The system shall..." vs. plain action statements; technical language vs functional language)
Length — how detailed or concise your requirements tend to be
Volume — approximately how detailed the set of requirements should be
Requirements Style and the Granularity Dial
If you have Requirements Style configured, it bypasses the Requirements Granularity Dial. Glossa will use your custom examples to determine the shape of generated requirements instead of the dial setting.
If you remove your style examples, the Granularity Dial will resume controlling requirement generation.
Tips for Good Examples
Cover your range. Choose examples that represent the variety of requirements you write — functional, complex, and simple — rather than all similar ones.
Use real requirements. Examples from actual past projects tend to produce better results than requirements written specifically for this setting.
Start with 5–7 examples. While 3 is the minimum, a few more gives Glossa a stronger signal, especially if your requirements vary across functional areas.