gsd-map-codebase

This skill automates codebase mapping by orchestrating four parallel agents that write seven structured architecture and convention documents directly into the .planning/codebase/ directory.

The best way to document a brownfield codebase is orchestrating parallel mapper agents to generate structured planning documents, capturing current architecture, conventions, and concerns non-intrusively without manual overhead.

Parallel agents generate codebase documentation through non-intrusive orchestration, where four mapper agents independently write seven predefined documents under .planning/codebase/ before the orchestrator validates completion.

Yes, you can refresh codebase mapping documents after major changes by re-invoking the parallel agent workflow, which overwrites the .planning/codebase/ files with updated architecture, structure, and test mappings.

You do not need an existing .planning/STATE.md file to map a codebase; the workflow loads state from STATE.md when present for continuity, but functions independently for fresh repository initialization.

A limitation of automated codebase architecture mapping is that the orchestrator only confirms completion without directly writing documents, meaning agents must autonomously capture all structural conventions and concerns accurately.