gsd-map-codebase

Map an existing codebase into seven structured documents under .planning/codebase/.

8|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-map-codebase-d0nmega
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-map-codebase
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-map-codebase
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-map-codebase-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill maps an existing codebase to a structured planning artifact, enabling a fast, shared understanding of current state before the next development phase.

Core Features & Use Cases

  • Four parallel gsd-codebase-mapper agents cover tech, architecture, quality, and concerns to produce seven documents under .planning/codebase/.
  • Provides a repeatable mapping workflow for brownfield projects, refreshes, and onboarding unfamiliar codebases.

Quick Start

Run the gsd-map-codebase skill to generate the codebase map under .planning/codebase/ and verify the seven documents are created.

Frequently Asked Questions about gsd-map-codebase

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

FAQPage Schema
How do I map an existing codebase to understand its architecture and conventions?▼

Mapping a codebase executes four parallel agents covering tech, architecture, quality, and concerns to generate structured documents under .planning/codebase/. This produces seven files including ARCHITECTURE.md and CONVENTIONS.md for complete structural visibility.

What's the best way to document an unfamiliar codebase before planning new development?▼

Documenting an unfamiliar codebase uses parallel mapper agents to produce seven structured planning artifacts under .planning/codebase/. These files capture tech stack, integrations, architecture, structure, conventions, testing, and concerns for shared team understanding.

Can I use parallel agents to generate documentation for a brownfield project?▼

Yes, brownfield project documentation generates through four parallel gsd-codebase-mapper agents. They produce STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, and CONCERNS.md, ensuring a repeatable mapping workflow for existing codebases.

Does codebase mapping verify that all planning documents are created successfully?▼

Codebase mapping verifies the seven generated documents exist under .planning/codebase/ after execution. It commits the complete map and presents recommended next steps such as /gsd-new-project or /gsd-plan-phase for continued development planning.

When do I need to generate a codebase map with structured planning artifacts?▼

A codebase map is needed when onboarding to unfamiliar code, refreshing documentation, or starting a new development phase on a brownfield project. It provides a fast, shared understanding of current state through seven structured documents covering tech, architecture, and quality.

What perspectives do the parallel mapper agents cover when mapping a codebase?▼

The parallel mapper agents cover tech, architecture, quality, and concerns perspectives. Each perspective contributes specific documents like STACK.md for tech, ARCHITECTURE.md for structure, and CONCERNS.md for potential issues, creating a comprehensive codebase overview.