Trace a product feature
Code Graph shows the wider engineering system. Feature Mapping gives you a focused implementation flow for one functional area of a repository.
Open Functions and name features
Open Functions. CodeZero first lists functional areas derived from the repository index. Before naming, these can appear as structural paths such as src/git or src/calendar.
Select Name all features to give the available areas human-readable names. Naming uses your existing Claude Code setup, and the resulting names are shared with your organisation.
A named feature can also contain sub-parts. Hover a sub-part to highlight the files involved, or click it to keep that highlight pinned while you read the map.
Read the feature map
Select a feature to open its flow. The map is arranged so the implementation reads from left to right:
- Entry — where requests or control enter the feature
- Goes Through — the implementation files and logic involved
- Reads / Writes — data touched by the feature
- Another repository — a dependency that crosses a repository boundary
Feature Mapping intentionally stays focused on the feature and its immediate relationships rather than expanding into the entire repository.
Code Graph versus Feature Mapping
Code Graph and Feature Mapping answer different questions:
- Code Graph
- Shows how the wider system is connected.
- Feature Mapping
- Shows how one functional area maps back to the code and dependencies that implement it.
Take the feature into Chat
Once you understand the feature flow, use it as the starting point for more specific questions:
- How does this feature currently work?
- Which repository owns each part of the flow?
- Where should this behaviour be extended?
- What would be affected if one part changed?
- Which tests should protect the implementation?
From there, Chat can investigate deeper implementation details or turn the requested change into a grounded plan.