map-codebase
Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
SKILL.mdskills/map-codebase/SKILL.md
GitHub<objective>
Analyze existing codebase using parallel bm-codebase-mapper agents. Each mapper explores a focus area and **writes documents directly** to `.planning/codebase/`; the orchestrator only receives confirmations, keeping context usage minimal.
Output: .planning/codebase/ folder with 7 structured documents about the codebase state. </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/map-codebase.md </execution_context> <context> Focus area: $ARGUMENTS (optional - if provided, tells agents to focus on specific subsystem)Load project state if exists: Check for .planning/STATE.md - loads context if project already initialized
This command can run:
- Before /gsd:new-project (brownfield codebases) - creates codebase map first
- After /gsd:new-project (greenfield codebases) - updates codebase map as code evolves
- Anytime to refresh codebase understanding</context>
Skip map-codebase for:
- Greenfield projects with no code yet (nothing to map)
- Trivial codebases (<5 files)</when_to_use>