Skill

gsd:map-codebase

From gsd

Analyzes codebase with parallel mapper agents to generate .planning/codebase/ documents on stack, integrations, architecture, structure, conventions, testing, and concerns. Use for brownfield projects, onboarding, refactoring prep, or refresh.

documentation

code-quality

npx claudepluginhub jnuyens/gsd-plugin --plugin gsd

Tool Access

This skill is limited to using the following tools:

ReadBashGlobGrepWriteTask

Preview

SKILL.md

Similar Skills

mapping-codebases

Analyzes existing codebases with parallel mapper agents to generate 7 structured docs on tech stack, integrations, architecture, structure, conventions, testing, and concerns in .planning/codebase/. For brownfield projects, onboarding, refactoring prep.

1 file3 tools

kata

cartographer

438

Orchestrates parallel subagents to map any codebase, creating docs/CODEBASE_MAP.md with architecture, file roles, dependencies, and navigation. Updates incrementally via git or scans.

1 file

cartographer

scan

Analyzes existing codebases by mapping structure, architecture, conventions, and concerns using parallel subagents. Checks for prior scans and supports refresh options.

1 file7 tools

pbr

Stats

Stars18

Forks3

Last CommitApr 24, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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.

<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/map-codebase.md </execution_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

<when_to_use> 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) </when_to_use>

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 4. Wait for agents to complete, collect confirmations (NOT document contents) 5. Verify all 7 documents exist with line counts 6. Commit codebase map 7. Offer next steps (typically: /gsd:new-project or /gsd:plan-phase)

<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>