Feature
A logical grouping of scenarios that represents a meaningful unit of the product — like “Document Upload” or “User Authentication.” Features form the structure of a living product specification.
A feature in a product specification is a named grouping of related scenarios. It represents a unit of the product that makes sense to the people who build, support, and manage it — not a technical component like a module or a class, but a recognisable area of behaviour that a PM or customer success manager would point to when answering a question.
Features can be nested up to two levels deep: a top-level feature like “Notifications” might contain sub-features like “Email Notifications” and “In-App Notifications.” This mirrors how teams naturally think about their product — broad areas that break down into more specific capabilities.
When Specsight analyses a codebase for the first time, it infers the feature structure from the code. Teams can then adjust the groupings manually — renaming, merging, or reorganising features to match how they think about their product. The feature tree becomes the table of contents of the living spec.
Related terms
- SPEC
Scenario
A single plain-language description of how a product behaves in a specific situation. The atomic unit of a living product specification.
- CONCEPT
Product Specification
A written description of how a product behaves — feature by feature, scenario by scenario. Distinct from a technical spec, which describes implementation.
- CONCEPT
Living Documentation
Documentation that is structurally incapable of falling out of sync with the product, because it is derived from the code rather than written separately.