map-codebase

You can generate structured codebase documentation automatically by orchestrating parallel mapper agents. These agents explore specific focus areas with isolated context and write structured documents directly to the .gsd/codebase/ folder.

Parallel codebase mapping is the process of spawning multiple specialized agents to analyze a software repository simultaneously. Each agent focuses on a specific area like tech stack or architecture, producing deterministic documentation.

Mapping a codebase architecture produces seven structured documents in the .gsd/codebase/ folder. These documents detail the technology stack, architecture, structure, conventions, testing, integrations, and concerns across the codebase.

Yes, you can use parallel agents to analyze your codebase conventions and tests. The orchestrator spawns specialized agents that operate with fresh context to explore the repository and write targeted documentation directly.

The best way to orchestrate codebase analysis without context limits is to spawn multiple agents with isolated context. The orchestrator only receives confirmations and line counts, preventing context overflow while generating comprehensive documentation.

No, you do not need to manually review the codebase before mapping software architecture. The orchestration skill automates repository analysis by spawning agents to reveal the technology stack, architecture, and conventions directly.