Feature Graph
A visual map of how features in a product depend on one another. Used to see the blast radius of a change before it ships.
A Feature Graph is a directed graph where each node is a Feature and each edge is a dependency between two Features — typically because one Feature calls into the code of another, or shares state with it. Specsight derives the graph automatically from the same codebase analysis that produces the spec, so the dependencies reflect what is actually wired up rather than what someone documented in a diagram years ago.
The graph answers a question every PM and engineering manager asks at some point: if we change this, what else does it touch? A Feature with many incoming edges is a foundation that other parts of the product rely on — risky to change. A Feature with no incoming edges is safe to deprecate. The graph makes both visible at a glance.
It is also a navigation tool. Click a node to open its Feature page; trace an edge to find related scenarios; pivot to the changelog of any Feature on the path. The graph and the spec are the same data, viewed two different ways.
Related terms
- SPEC
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.
- SPEC
Changelog
A chronological record of what changed in a product, feature, or scenario over time. In Specsight, every Feature carries its own.
- SPEC
Scenario
A single plain-language description of how a product behaves in a specific situation. The atomic unit of a living product specification.