gabrielmoreira Each mapper agent 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.
Parse the first token of $ARGUMENTS:
- If it is
--fast: strip the flag, then read and execute~/.claude/gsd-core/workflows/scan.md(passing remaining args including optional --focus). Load it on demand here — it is deliberately not in<execution_context>, so the common full-map path does not pay for it. - If it is
--query: strip the flag, run the intel workflow (passing remaining args as the subcommand). - Otherwise: pass all of $ARGUMENTS as focus area to the map-codebase workflow.
Load project state if exists: Check for .planning/STATE.md - loads context if project already initialized
This command can run:
- Via /gsd-onboard for first-time brownfield setup - creates codebase map first
- After /gsd-new-project (greenfield codebases) - updates codebase map as code evolves
- Anytime to refresh codebase understanding
Skip map-codebase for:
- Greenfield projects with no code yet (nothing to map)
- Trivial codebases (<5 files)