gsd-map-codebase

You can generate architecture documentation for an unfamiliar codebase by running a parallel mapping workflow that analyzes the source and produces seven structured planning documents in a .planning/codebase directory. These files cover stack, integrations, architecture, and conventions to guide onboarding.

Before a major codebase refactor, you should create seven standardized planning documents: STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, and CONCERNS.md. This bundle ensures deterministic, version-controllable outputs to guide your refactoring decisions.

Parallel mapper agents analyze an existing codebase by coordinating orchestration across different codebase areas simultaneously. This parallel processing generates a comprehensive planning bundle that captures your project's architecture, structure, and testing conventions efficiently.

Yes, you can use automated codebase mapping for brownfield project onboarding. The workflow provides brownfield readiness by generating consistent, deterministic planning outputs that help new team members understand the existing architecture and integrations quickly.

The best way to maintain version-controllable codebase documentation is to generate a standardized .planning/codebase directory structure. This deterministic output supports ongoing updates and ensures your planning documents remain synchronized with your codebase during future development.

Yes, codebase mapping works without external dependencies or components. The workflow operates independently to analyze your source code and produce the seven structured planning documents required for downstream workflows and architecture decisions.