gsd-map-codebase

To generate codebase documentation before refactoring, this skill coordinates parallel mapper agents to examine your project and produce seven standardized planning documents under .planning/codebase/, covering architecture, structure, conventions, and concerns.

The best way to map an unfamiliar codebase for onboarding is using parallel agents to analyze and document the current state, generating structured files like STACK.md, ARCHITECTURE.md, and CONCERNS.md to accelerate understanding.

Yes, you can automate codebase analysis with parallel agents. This skill launches four specialized mapper agents simultaneously to examine the codebase and validate seven distinct planning documents before committing the results.

When assessing a brownfield project, the generated planning documents include STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, and CONCERNS.md, summarizing the current codebase state.

Yes, this codebase mapping approach works for ongoing maintenance. It re-examines the existing codebase to update the seven standardized planning documents under .planning/codebase/, ensuring the documentation reflects the current state.

Using parallel mapper agents instead of a single agent for codebase documentation allows specialized agents to concurrently generate different documents like ARCHITECTURE.md and TESTING.md, reducing wait time and ensuring comprehensive coverage.