This is a live demo — explore a slice of Specsight's own product spec, generated from its codebase. The full spec is much larger.
This is a live demo — explore a slice of Specsight's own product spec, generated from its codebase. The full spec is much larger.
| Context | Action | Outcome |
|---|---|---|
HP-36 code merged to the monitored branch of a connected project Action Specsight detects the change and starts a sync Outcome project status changes to syncing, spec stays visible to members | Specsight detects the change and starts a sync | project status changes to syncing, spec stays visible to members |
HP-37 code change with new product behaviour detected during sync Action Specsight adds a new scenario to the relevant feature Outcome scenario appears with a Created badge and a changelog entry is recorded |
This early exit was the biggest efficiency gain in the sync pipeline. Roughly 60-70% of merges contain no product behaviour changes — style fixes, docs, config. Catching those early avoids running a full analysis unnecessarily.
Specsight adds a new scenario to the relevant feature |
scenario appears with a Created badge and a changelog entry is recorded |
HP-38 code change with modified product behaviour detected during sync Action Specsight updates the matching scenario Outcome scenario updated, changelog records the before and after values | Specsight updates the matching scenario | scenario updated, changelog records the before and after values |
HP-39 code change with removed product behaviour detected during sync Action Specsight marks the scenario as deleted Outcome scenario soft-deleted, recorded in the changelog as Deleted | Specsight marks the scenario as deleted | scenario soft-deleted, recorded in the changelog as Deleted |
HP-40 completed sync with scenario changes Action Specsight sends notifications to enrolled members Outcome email summarises created, updated, and deleted scenarios | Specsight sends notifications to enrolled members | email summarises created, updated, and deleted scenarios |
EC-25 code change limited to style fixes, documentation, or config Action Specsight evaluates the diff before running a full analysis Outcome sync short-circuited, no scenarios updated | Specsight evaluates the diff before running a full analysis | sync short-circuited, no scenarios updated |
EC-26 manually added scenario in a feature affected by a code change Action Specsight processes the feature during sync Outcome manual scenario preserved unchanged, retains its Manually Added label | Specsight processes the feature during sync | manual scenario preserved unchanged, retains its Manually Added label |
ER-20 organisation at 100% of its monthly sync limit Action Specsight receives a push event for a connected project Outcome sync silently skipped, no scenarios updated until next billing period or upgrade | Specsight receives a push event for a connected project | sync silently skipped, no scenarios updated until next billing period or upgrade |
ER-21 unrecoverable error during sync Action background task fails after retries Outcome sync marked as failed, project returns to its previous state | background task fails after retries | sync marked as failed, project returns to its previous state |