mcpbeat

Gsd Map Codebase

coco-research/gsd-map-codebase

Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents

649 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
196
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/coco-research/coco --skill gsd-map-codebase

The instruction itself

as written by the author

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

<execution_context>

@$HOME/.claude/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 /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>

<process>

  • Check if .planning/codebase/ already exists (offer to refresh or skip)
  • Create .planning/codebase/ directory structure
  • 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
  • Wait for agents to complete, collect confirmations (NOT document contents)
  • Verify all 7 documents exist with line counts
  • Commit codebase map
  • Offer next steps (typically: /gsd-new-project or /gsd-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>

How to use it

Copy the folder

Take coco-research/gsd-map-codebase from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.