gsd-map-codebase

npx skills add majiayu000/claude-skill-registry --skill gsd-map-codebase-davepoon-buildwithclaude --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

<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> <!-- Workflow content (was: map-codebase.md) --> <purpose> Orchestrate parallel codebase mapper agents to analyze codebase and produce structured documents in .planning/codebase/ Each agent has fresh context, explores a specific focus area, and **writes documents directly**. The orchestrator only receives confirmation + line counts, then writes a summary. Output: .planning/codebase/ folder with 7 structured documents about the codebase state. </purpose> <available_agent_types> Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'): - gsd-codebase-mapper — Maps project structure and dependencies </available_agent_types> <philosophy> **Why dedicated mapper agents:** - Fresh context per domain (no token contamination) - Agents write documents directly (no context

if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
ls -la .planning/codebase/
mkdir -p .planning/codebase
wc -l .planning/codebase/*.md
Check for common API key patterns in generated docs
node "$GSD_TOOLS" commit "docs: map existing codebase" --files .planning/codebase/*.md