gsd-map-codebase

Map a codebase into seven planning documents under `.planning/codebase/`.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-map-codebase-jedmamosto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-map-codebase
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-map-codebase
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-map-codebase-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gsd-map-codebase eliminates the time-consuming guesswork of understanding an unfamiliar or changing repository by generating a structured, up-to-date codebase map in your planning folder.

Core Features & Use Cases

  • Parallel codebase mapping: Runs multiple mapper agents across tech, architecture, quality, and concerns, then consolidates their outputs into .planning/codebase/.
  • Configurable scan modes: Uses a full map by default or a faster scan mode for targeted analysis; supports query-style operations to check status, diffs, or refresh mappings.
  • Change-aware workflows: Creates the map for brownfield projects, refreshes it after significant changes, and helps onboarding or pre-refactor planning.

Quick Start

Run gsd-map-codebase from the project root to generate the full parallel codebase documents under .planning/codebase/.

Frequently Asked Questions about gsd-map-codebase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate documentation for an existing codebase to speed up onboarding?

Codebase mapping generates structured repository intelligence by running parallel agent sweeps across tech, architecture, quality, and concerns to produce planning documents. It consolidates outputs into a `.planning/codebase/` folder with seven required documents for faster navigation and refactoring.

Can I refresh repository documentation after making significant code changes?

Yes, codebase mapping supports iterative refresh cycles for brownfield projects where code state changes over time. You can use query-style operations to check repository status, review diffs, and refresh the existing `.planning/codebase/` mappings to keep documentation current.

What is the best way to map a large repository for pre-refactor planning?

Codebase mapping uses parallel mapper agents to analyze technology, architecture, quality, and concerns simultaneously. This parallel sweep approach generates comprehensive planning documents under `.planning/codebase/`, providing a structured view of the repository for safer refactoring decisions.

Does codebase mapping support a faster scan mode for targeted architecture analysis?

Yes, codebase mapping offers configurable scan modes including a full map by default and a faster scan mode for targeted analysis. It also supports query-style operations to check status or diffs without generating the complete seven-document structure.

What documents are generated when mapping a codebase for project planning?

Codebase mapping produces a `.planning/codebase/` folder containing seven required documents. These documents cover repository intelligence across technology, architecture, code quality, and concerns discovery, generated through parallel mapper agents for comprehensive project planning.