The spec is a tree of features on the left; each feature opens to a list of scenarios on the right. Specsight infers both from the codebase, and you can edit either by hand.
Features
A feature is a recognisable area of behaviour — "Sign-in", "Billing", "Email notifications". Features can nest up to two levels (feature → sub-feature → sub-sub-feature). Click one in the left rail to open it.
Click the + at the top of the rail for New feature (Name, Parent, Description). To rename or remove, open the feature and use the actions menu next to the title: Edit name & description or Delete feature.
Scenarios
Each scenario describes one behaviour in Context, Action, Outcome form:
- Context — the starting state. "A user is signed in and viewing the dashboard."
- Action — what someone or something does. "They click the export button."
- Outcome — what the product does in response. "Specsight downloads an XLSX file with all scenarios."
Every scenario carries one of three categories: Happy path (the normal route), Edge case (boundary conditions), or Error (failure modes).
Scenarios or flow diagram
Two tabs sit just below the feature title. Scenarios (the default) lists every Context, Action, Outcome row. Flow diagram draws the same feature as a user flow, with each part of the diagram citing the scenarios behind it — useful when you want to see how the feature fits together. See feature map for the full drill-down.
Find and filter
A toolbar above the scenarios offers three controls:
- Category chips — All, Happy, Edge, Error narrow the list to one category
- Search scenarios — matches across Context, Action, and Outcome text
- View toggle — List view groups scenarios by Context; Table view shows Context, Action, Outcome as columns
Add, edit, delete
- Add — click New scenario, pick a category, type a Context (or pick one from the suggestions), fill in Action and Outcome, then Create scenario.
- Edit — click a scenario to open the side panel, click Edit, then Save changes.
- Delete — open the side panel, click Delete, then confirm with Delete scenario. The deletion is recorded in the changelog.
Adding, rewording, or deleting a scenario redraws that feature’s user flow a minute or so later, so the diagram keeps matching the scenarios. A run of quick edits redraws once, at the end.
Admins, Developers, and Editors can add, edit, and delete. Viewers read but cannot change — see members and roles.