research_codebase_nt

To document an existing codebase architecture for onboarding, you can generate factual markdown files describing code structure, component interactions, and implementation details without adding subjective evaluations or recommendations.

The best way to create knowledge transfer documentation is to synthesize the codebase into structured markdown, mapping out component interactions and implementation details objectively to facilitate clear understanding.

Yes, you can analyze a codebase without receiving refactoring recommendations by using an objective documentation approach that focuses solely on describing what exists, how it works, and where it is located.

To map component interactions and implementation details in a codebase, execute parallel agents for comprehensive research and synthesize their findings into structured markdown documents for clear knowledge transfer.

Yes, codebase documentation works for understanding specific modules by providing an unbiased map of the module's files, functions, and their relationships for new developers joining a project.