gsd-map-codebase

<objective> Analyze existing codebase using parallel gsd-codebase-mapper agents to produce structured codebase documents.

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. </objective>

<executioncontext> @{{PLATFORMROOT}}/get-shit-done/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 {{COMMAND_PREFIX}}new-project (brownfield codebases) - creates codebase map first
• After {{COMMAND_PREFIX}}new-project (greenfield codebases) - updates codebase map as code evolves
• Anytime to refresh codebase understanding

</context>

<whentouse> Use map-codebase for:

• Brownfield projects before initialization (understand existing code first)
• Refreshing codebase map after significant changes
• Onboarding to an unfamiliar codebase
• Before major refactoring (understand current state)
• When STATE.md references outdated codebase info

Skip map-codebase for:

• Greenfield projects with no code yet (nothing to map)
• Trivial codebases (<5 files)

</whentouse>

<process>

1. Check if .planning/codebase/ already exists (offer to refresh or skip)
2. Create .planning/codebase/ directory structure
3. Spawn 4 parallel gsd-codebase-mapper agents:

- Agent 1: tech focus → writes STACK.md, INTEGRATIONS.md - Agent 2: arch focus → writes ARCHITECTURE.md, STRUCTURE.md - Agent 3: quality focus → writes CONVENTIONS.md, TESTING.md - Agent 4: concerns focus → writes CONCERNS.md

1. Wait for agents to complete, collect confirmations (NOT document contents)
2. Verify all 7 documents exist with line counts
3. Commit codebase map
4. Offer next steps (typically: {{COMMANDPREFIX}}new-project or {{COMMANDPREFIX}}plan-phase)

</process>

<success_criteria>

• .planning/codebase/ directory created
• All 7 codebase documents written by mapper agents
• Documents follow template structure
• Parallel agents completed without errors
• User knows next steps

</success_criteria>