Weekly digest · 11 Oct

Scheduled5 Oct 2026 – 11 Oct 2026

+11 added~13 edited−1 deletedacross 7 features· 4 releases

The feature map opens on main features, releases have titles and summaries, and first analyses are no longer counted as changes.

Key changes

- Clicking a sub-feature opens its user-flow diagram, with a way back to the main feature's map
- Features from outside a sub-feature map that connect to it appear on that map too
- Hovering a line between features lists each connection behind it and the sub-features it joins
- Search finds a main feature by the name of any of its sub-features
- Show all changes opens every feature's changes at once, and Hide all changes closes them
- Each change can be opened to see edits before and after, plus added and deleted items
- The reason behind a highlighted change now shows directly, without hovering
- New features are tagged New and listed first
- The changelog can be filtered to show only what touched one feature
- The changelog shows a First analysis entry with feature counts and a link to the project
- Recent activity labels it First analysis or Re-analysis
- Digests list only later changes, or say when tracking began
- New release notes no longer pre-tick everything; they say when tracking started
- Asking what changed recently now lists releases by title, newest first

Also changed

Long answersAsk now says when an answer was cut short and suggests asking a narrower question.
Feature namesNew or renamed features are now saved in title case, keeping small words like of lowercase.
Stuck map runsThe feature map now waits 75 minutes, up from 45, before giving up on a stuck run.

What it means for…

Support(what customers will notice)Starting a fresh analysis now warns that the project's changelog history will be replaced, so customers may ask whether past entries can be kept.Customers whose release notes look empty after a first analysis should expect changes to appear only after their next update to the code.

Feature Map

+4 added~4 edited−1 deleted

ContextActionOutcome

user on the feature map pageviews the page~~Was: a graph of every feature is rendered, with labelled lines showing how they connect~~only top-level features are drawn; lines show where any of their features connect

user on the feature map page~~Was: clicks a feature node~~clicks a feature with no sub-features~~Was: the feature opens as a user-flow diagram: the screens people move through, the actions on the arrows between them, and the checks and responses along the way~~its user-flow diagram opens, showing screens, the actions between them, and the product's checks

user on the feature map pagetypes in the search box~~Was: matching feature nodes are highlighted and the rest are dimmed~~features matching by name or by a sub-feature are highlighted; the rest are dimmed

~~Was: user on a project whose diagram run has been stuck for over 45 minutes~~user on a project whose diagram run has been stuck for over 75 minutesviews the feature mapthe run is given up on rather than spinning forever; admins and developers get the option to try again

user on the feature map pageclicks a feature that has sub-featuresits sub-feature map opens; features outside it that connect show as dotted boxes

user on a sub-feature mapclicks a sub-featureits user-flow diagram opens, with a trail back to the parent's map

user on the sub-feature map of a feature with its own scenariosviews the mapfeature's own box sits among its sub-features, opening its own flow

user on the feature map pagehovers a line between two featureseach connection behind it is listed by type, naming any sub-features it joins

~~user on a feature whose scenarios all sit in its sub-featuresopens its flow diagrama note explains the scenarios live in the sub-features and points them to open one of those instead~~

Changelog

+5 added~4 edited

ContextActionOutcome

user on the changelog pagescrolls back to the first analysis~~Was: analysis reads as a Specsight sync, with every scenario counted as added~~"First analysis" card shows the spec's feature and scenario counts and a View spec link

user on the changelog pageviews the page~~Was: changes are grouped by day; each sync entry shows the added, changed, and removed counts at a glance~~changes grouped by day; each release shows its title, summary, counts, and changed features

user on the changelog pageopens a release~~Was: the entry opens into a per-feature, per-scenario breakdown showing the before and after of every changed field~~release page shows one card per feature with a one-line summary, its changes folded

user on a release with a highlighted change~~Was: hovers or focuses the Highlight badge~~views the release~~Was: a one-sentence, plain-language reason explains what changed and who it affects~~plain-language reason shows under the change; highlighted changes stay visible when the rest fold

user on the changelog pagefilters the list by featurelist narrows to releases, edits, and annotations that touched that feature

user on a release that changed several featureschooses Show all changesevery feature card unfolds to list all its changes; Hide all changes folds them

user on a releaseexpands a changeedited fields show before and after; added scenarios in full, deleted ones struck through

user on a release that created a featureviews the releasefeature tagged New on the changelog list and release page, ahead of the others

user on a releasechooses a question under Ask about this releaseAsk opens with that question answered for this release alone; follow-ups stay on it

Ask Specsight

+1 added~1 edited

ContextActionOutcome

user in the Ask areaasks a question whose answer runs past the length limitanswer closes with a line saying it was cut short, suggesting a narrower question

user in the Ask areaasks what changed recently~~Was: a written answer streams in with an inline what-changed card grouping the recent changes from the changelog~~answer streams in above a Changes card listing each release by title, newest first

Projects

~2 edited

ContextActionOutcome

admin or developer on the project danger zonestarts a fresh analysis and chooses whether to keep manually added scenarios~~Was: confirmation shows the organisation's re-analyses left this month; fresh analysis queued, spec stays visible~~confirmation warns changelog history is replaced, shows re-analyses left; fresh analysis queued, spec stays visible

user on the project overview soon after an analysisviews the recent activity card~~Was: analysis appears as a Specsight sync row, every scenario counted as added~~analysis appears as a "First analysis" or "Re-analysis" row that opens the spec

Feature Tree & Scenarios

+1 added

ContextActionOutcome

editor on the spec pagecreates or renames a feature with a lowercase namename saved in Title Case; small words like of and with stay lowercase mid-name

Digests

~1 edited

ContextActionOutcome

user viewing a digest covering the first analysisopens the digest~~Was: analysis counted as a release, with every scenario in the spec listed as added~~analysis isn't a release; digest lists only later changes, or says when tracking started

Release Notes

~1 edited

ContextActionOutcome

editor on the release notes list of a newly analysed project, nothing shipped yetstarts new release notes~~Was: drafting page ticks every scenario from the analysis as a change to announce~~drafting page says when Specsight started following; changes appear after the next merge