Your spec is a tree of features, each opening to a list of scenarios. Specsight infers both from your code, and you can edit either by hand. Open Product spec in the project rail.
Features
A feature is a recognisable area of behaviour, like Sign-in, Billing or Email notifications. Features nest up to two levels.
Click + in the feature tree for New feature, with Name, Parent and Description. To rename or remove one, open it and use the actions menu: Edit name & description or Delete feature.
Scenarios
Each scenario describes one behaviour as Context, Action, Outcome:
- Context — the starting state, like "a user is signed in and viewing the dashboard"
- Action — what someone or something does, like "they click the export button"
- Outcome — what the product does in response, like "an XLSX file downloads"
Every scenario carries one category: Happy path for the normal route, Edge case for boundary conditions, Error for failure modes.
Switch views
- Scenarios — every Context, Action, Outcome row
- Flow diagram — the same feature drawn as a user flow, each part citing the scenarios behind it
- Sub-feature map — how the feature’s sub-features connect, for a feature that has them
Find and filter
- All, Happy, Edge, Error — narrow the list to one category
- Search scenarios — matches Context, Action and Outcome text
- List view and Table view — group by Context, or show the three as columns
Add, edit, delete
- Add — click New scenario, pick a category, fill in Context, Action and Outcome, then Create scenario
- Edit — click a scenario, click Edit, then Save changes
- Delete — click a scenario, click Delete, then confirm with Delete scenario
A deletion is recorded in Changes. Adding, rewording or deleting a scenario redraws that feature’s user flow.