Codebase context

To map a new feature idea to your codebase, generate a lightweight context artifact that anchors decisions to existing modules, API surfaces, data models, and deployment boundaries. This identifies a minimal set of touched files, about 10–25, to guide where to extend versus create new code.

A codebase context map is a lightweight markdown artifact that analyzes multi-module repos by anchoring ideas to existing constraints and extension points. It covers API surfaces, core logic, data models, UI, tests, and deployment boundaries to minimize greenfield assumptions during development.

Identify files to modify by generating a repo-aware context map that references canonical paths and highlights extension points. The map isolates a minimal set of approximately 10–25 touched files, ensuring you extend existing modules rather than unnecessarily creating new ones.

Yes, codebase context analysis applies to multi-module repos with API surfaces, core logic, data models, UI, tests, and deployment boundaries. It maps these areas to anchor your ideas and guide future work across all these architectural layers.

Store codebase context documentation at docs/forge/ideas/<IDEA_ID>/latest/codebase_context.md along with a run snapshot. This canonical pathway ensures traceability and stable artifact generation anchored to your specific IDEA_ID.

The best way to minimize greenfield assumptions is producing a repo-aware codebase map that identifies extension points and architectural boundaries. By anchoring decisions to existing modules and constraints, you clearly guide where to extend versus where to create.