From-code, then human-reviewed
Automated inference is a starting point, not the finish line. Agents propose domains and features with path evidence when possible; you confirm business intent, rename for clarity, and fill gaps the code cannot reveal.
Guide
How do I create a product map from an existing codebase?
Start from the repo you already have. Kriyastream can infer product structure from code, then you review, correct, and use the map for planning and agent context.
Learn from public maps
The public Product Maps directory shows how real open-source products look when structured as Domain → Feature. Use them as references while building your own from-code map.
How to do it
- 1Connect or select the repository that represents the product.
- 2Run from-code map generation to draft the Product Map.
- 3Review inferred facets; keep, merge, or rewrite for accurate product language.
- 4Check score and gaps; prioritize improvements.
- 5Export structure into work breakdown when you are ready to execute.
FAQ
What if the repo is a monorepo?
Map the product surface you care about first (the customer-facing app or primary service). You can expand to other packages as separate domains or related maps.
Can I start from a public map instead?
Yes. Clone the shape of a comparable public map, then align it to your code — useful when your repo is early or sparse.