researching-codebase

To map codebase architecture before planning, document where a feature resides by capturing file paths, data flow paths, interfaces, and module boundaries. This provides the necessary context for an AI agent to reason about the system design without making direct source code edits.

The best way to document where a domain module is implemented is to trace its behavior across files and lines, identifying key interfaces and architectural placement. This records code ownership and responsibilities to support informed planning and avoid rework.

Analyzing a codebase helps with system design by revealing how data flows across modules and documenting their interfaces and boundaries. This traces implementation paths to clarify code ownership and architectural responsibilities without modifying the source.

Yes, you can trace implementation paths and locate code without modifying source files. The process specifically captures where code resides, including files and lines, and maps data flow paths so an AI agent can reason about the system safely.

You need to trace data flow paths and module boundaries when asked how a domain works, where a specific feature is implemented, or when you need architectural context before planning. This prevents rework by clarifying system design and code ownership.

Yes, mapping codebase context captures exact file paths, line numbers, interfaces, and module boundaries. This documentation allows an AI agent to understand the architectural placement and data flow of a feature to support accurate planning.