gsd-map-codebase
Uses parallel agents to produce comprehensive documentation on codebase state and architecture.
Install
mkdir -p .claude/skills/gsd-map-codebase && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10269" && unzip -o skill.zip -d .claude/skills/gsd-map-codebase && rm skill.zipInstalls to .claude/skills/gsd-map-codebase
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Analyze codebase with parallel mapper agents to produce .planning/codebase/ documentsKey capabilities
- →Map codebase state
- →Generate technical documentation
- →Analyze architectural structure
- →Identify technical debt
How it works
It spawns parallel mapper agents to inspect the codebase and write structured documentation files for technical, architectural, and quality aspects.
Inputs & outputs
When to use gsd-map-codebase
- →Map current codebase state
- →Generate documentation of technical debt
- →Analyze architectural structure
About this skill
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>
<execution_context> @.github/get-shit-done/workflows/map-codebase.md </execution_context>
<flags> - **--fast**: Lightweight scan mode — spawns one mapper agent instead of four. Accepts an optional `--focus` value: `tech`, `arch`, `quality`, `concerns`, or `tech+arch` (default). Faster and lower-context than the full map. - **--query**: Codebase intelligence query mode. Sub-commands: `query <term>`, `status`, `diff`, `refresh`. Requires intel to be enabled in config (`intel.enabled: true`). Runs inline for query/status/diff; spawns an agent for refresh. - **(no flag)**: Full parallel map — spawns 4 mapper agents to produce all 7 codebase documents. </flags> <context> Arguments: $ARGUMENTSParse the first token of $ARGUMENTS:
- If it is
--fast: strip the flag, run the scan workflow (passing remaining args including optional --focus). - 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:
- 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>
<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>
<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>
When not to use it
- →Greenfield projects with no code
Prerequisites
Limitations
- →Not for trivial codebases (<5 files)
How it compares
It automates the creation of a codebase map using parallel agents rather than manual documentation.
Compared to similar skills
gsd-map-codebase side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gsd-map-codebase (this skill) | 0 | 3mo | No flags | Intermediate |
| product-manager-toolkit | 32 | 7mo | Review | Beginner |
| gathering-requirements | 3 | 8mo | No flags | Intermediate |
| ideate | 1 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by wikiepeidia
View all by wikiepeidia →You might also like
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
gathering-requirements
CaptainCrouton89
Systematically clarify user needs, preferences, and constraints before planning or implementation. Classifies work type, investigates existing systems, discovers edge cases and integration points, resolves assumptions, and creates detailed specifications. Use when building features, enhancements, or integrations where requirements need clarification.
ideate
liveloveapp
Capture and document a new idea in this repo. Use when the user says things like "help me brainstorm", "I have an idea", or "let's capture this for the future" and wants it recorded in `design/ideas/` with a summary, supporting research (repo context + web if useful), and a sketch.
rfc
jiangzhe
Design and resolve RFC documents through evidence-gated multi-round workflow. Use when planning large architectural/program-level changes in docs/rfcs, enforcing goal/scope/direction clarity, explicit first-principles/long-term/original-fit proposal lenses with rationale, draft-to-formal progression
idea-extraction
RepairYourTech
Exhaustive idea extraction through recursive breadth-before-depth exploration with Deep Think protocol and fractal structure. Use during /ideate to transform raw ideas into comprehensive, structured ideation output. Writes to a fractal folder hierarchy — every node has an index, CX file, and childre
catch-me
junjunjunbong
Start or refresh domain onboarding for the current project. Generates persona, lexicon, signaling, anti-patterns, first-week plan, and a project-specific playbook for a chosen profession.