gsd-map-codebase

To generate structured codebase documentation, you can automate the analysis process using parallel mapper agents that scan your project and output seven distinct documents covering technology stack, architecture, conventions, testing, and concerns into a designated directory.

The best way to map an unfamiliar codebase for onboarding is using parallel analysis agents to simultaneously evaluate technology, architecture, quality, and concerns, generating structured documentation files for quick reference.

Yes, you can analyze a specific area of your project instead of the entire codebase by specifying a target directory like 'api' when running the analysis, generating structured documentation scoped to that section.

You should run codebase analysis on a greenfield project anytime as it evolves to refresh the structured documentation map after significant changes, ensuring your technology stack and architecture records stay current.

Mapping a codebase generates seven distinct documents: STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, and CONCERNS.md, stored within the .planning/codebase/ directory.