devlyn:discover-product

Feature tracing in a codebase follows execution paths from user-facing routes and major UI components through state management and backend endpoints to understand what each implemented capability actually does.

Discovering implemented features involves scanning project directory architectures to locate user-facing routes, UI components, backend endpoints, and core state logic, then converting these real implementations into a feature-oriented markdown document.

Yes, this approach covers both web app and service architectures by analyzing backend integrations and tracing feature scope across common directories to identify implemented and unimplemented items.

The best way to document actual software capabilities is converting real codebase implementations into a stakeholder-ready markdown document, avoiding assumptions based on filenames or marketing claims by reading metadata and tracing implementation code.

A limitation of tracing feature scope through route analysis is that it requires reading metadata files and implementation code across common directories, meaning incomplete repositories or missing backend integrations may result in unreported features.