gsd-map-codebase

You can automatically generate codebase documentation by running a workflow that spawns parallel agents to explore the repository and write structured documents covering architecture, structure, conventions, tests, and concerns into the .planning/codebase/ directory.

Parallel agent orchestration for mapping a codebase is a process where an orchestrator spawns multiple agents simultaneously to explore different focus areas, aggregate confirmations, and produce structured documentation while preserving context isolation to avoid heavy prompt usage.

You can map codebase architecture and structure into planning documents by executing a mapping workflow that generates seven structured files within the .planning/codebase/ directory, capturing the current state of the repository for brownfield projects and ongoing code evolution.

Yes, you can use parallel agents to document a brownfield codebase. The mapping workflow supports existing projects by generating seven structured documents that detail the architecture, structure, conventions, testing setup, and current concerns within the .planning/codebase/ directory.

The best way to document code conventions and testing setup automatically is using a parallel agent workflow that explores the repository focus areas and outputs structured documentation files detailing conventions, tests, and architectural concerns into .planning/codebase/.

Mapping a large codebase requires context isolation and parallel agents to avoid heavy prompt usage. The orchestrator coordinates four parallel agents to explore focus areas independently, guaranteeing end-to-end mapping while aggregating confirmations efficiently.