The feature map shows how a project fits together. The top level is every feature and the relationships between them. Click a feature to drill in and see the user flow inside it, drawn from its scenarios.
Specsight infers the map during analysis and updates it during automatic syncs. The canvas is read-only.
Open the map
In the project rail, click Feature map. The top-level view loads auto-fitted to the viewport.
Move around
- Pan — drag the canvas background
- Zoom — scroll, or use the zoom controls top-right
- Fit to view — the fit button recentres so every node is visible
- Fullscreen — the expand button hides the rail; Esc exits
- Hover a feature — its connected features stay raised; the rest dim
- Hover an edge — a tooltip shows the connection type and label
- Search features — the input in the header filters by name; matches stay raised, the rest dim
Connection types
Edges between features are labelled with one of nine types:
- Leads to — one feature's output feeds into another
- Triggers — an action in one starts another
- Depends on — one requires another to function
- Shares data — two features exchange data
- Authenticates — one handles auth for another
- Notifies — one sends alerts to another
- Configures — one provides settings for another
- Extends — one adds capabilities to another
- Validates — one checks another's rules
Drill into a feature
Click a feature to redraw the canvas as its user flow: where people can be, what they do, what the product checks, and what it gives back. Specsight draws it from that feature’s own scenarios. Zoom, pan and fullscreen work the same as on the top level; the search input is on the top-level map only.
Each card is one of six kinds. Three of them carry a small icon in the top-right corner — hover it for a one-line explanation.
| Card | What it means |
|---|---|
| Screen | A page, modal or panel the user is on |
| Question | Something the product checks — the answers ride the arrows leaving it |
| System step | The product acting on its own, with a gear icon |
| Result | What the product shows or produces when a journey ends where it started |
| Outside | Somewhere beyond the product — an email inbox, a payment provider — with a globe icon |
| Waiting | The user is waiting for something, with a clock icon |
Cards where a journey starts or stops also carry a badge: Start where people enter, End where a journey completes, Error where it is blocked and the user cannot continue without backtracking or help. Questions and system steps never carry one — nothing rests there.
Read the arrows
- Hover an arrow — the action that moves someone along it appears, like "clicks Check out"
- Answers stay visible — an arrow leaving a question carries its short answer, like "expired", so branches read at a glance
- A dashed arrow — the step happens on its own, with nothing for the user to do
See the scenarios behind anything
Click any card or arrow to open the detail panel. It names what you picked and lists the scenarios that evidence it, each with its full Context / Action / Outcome and its category. Click one to jump straight to that scenario in the spec.
One scenario can evidence several parts of the flow, and one card can rest on several scenarios. Some elements cite none — the panel says so — because the diagram draws the shape of the feature, not one box per scenario.