Digest
A plain-language summary of what changed in a product. Specsight emails one to the team each week, and you can generate one for any time range, so the whole company stays in the loop.
A digest is a Specsight-generated document covering a specific time window: the last sprint, the past month, since the last board meeting. It pulls together every release that landed in that window and tells what changed in plain words: the updates people would describe, then what they mean for support, sales and marketing, with the details behind each update one click away.
Digests exist because the changelog answers a different question. The changelog is per-feature and continuous, useful for tracing the history of one specific behaviour. A digest is per-period and aggregated, useful when someone asks "what changed last quarter?" and the right answer is a tidy summary, not a sprawling per-feature audit trail.
The output is faithful by design. Every line is grounded in a change Specsight observed in the window, while release notes are the curated, customer-voiced counterpart. Each week the team gets one by email, with what the changes mean for support, sales and marketing; generate one on demand before a board meeting or a client review.
Related terms
- SPEC
Changelog
A chronological record of what changed in a product, feature, or scenario over time. In Specsight, one running changelog covers the whole product, filterable down to a single feature.
- OPERATIONS
Release Notes
A curated, customer-facing announcement of what changed in a product. In Specsight, drafted from the changes you pick, written in your product’s voice, and published to a public page.
- OPERATIONS
Sync
The release-triggered update to a Specsight spec. Fires automatically every time code lands on the tracked branch, touching only the scenarios that release changed.
- SPEC
Scenario
A single plain-language description of how a product behaves in a specific situation. The atomic unit of a Specsight spec.