gsd-map-codebase

Coordinate parallel gsd-codebase-mapper agents to generate a seven-document codebase map.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill gsd-map-codebase-rkz91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-map-codebase
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-map-codebase
Command: npx skills add https://github.com/rkz91/coco --skill gsd-map-codebase-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze codebases by orchestrating parallel gsd-codebase-mapper agents to generate a structured, developer-friendly map stored under .planning/codebase/ for quick onboarding and future maintenance.

Core Features & Use Cases

  • Parallel mapper agents explore distinct focus areas (tech, architecture, quality, concerns) and write dedicated documents to .planning/codebase/.
  • Produces seven documents (STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, CONCERNS.md) that collectively capture the current state of the codebase.
  • Ideal for brownfield onboarding, pre-refactor planning, and knowledge transfer when joining unfamiliar projects; supports ongoing codebase evolution.

Quick Start

Run the gsd-map-codebase workflow to generate the .planning/codebase/ map and its seven documents.

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 before refactoring?

To generate documentation for an existing codebase before refactoring, you can orchestrate parallel agents to analyze the project and produce a structured map under .planning/codebase/. This map captures current architecture, structure, conventions, and concerns for quick onboarding and maintenance.

What is the best way to map codebase architecture and conventions for new team members?

The best way to map codebase architecture for new team members is using parallel agents that explore distinct focus areas like tech, architecture, and quality. They generate seven dedicated documents including STACK.md, ARCHITECTURE.md, and CONVENTIONS.md for comprehensive knowledge transfer.

Can I analyze a brownfield project in parallel to capture its current tech stack and concerns?

Yes, you can analyze a brownfield project by coordinating parallel agents that explore distinct focus areas. They write dedicated documents to .planning/codebase/, capturing the current tech stack, integrations, architecture, and concerns for future maintenance.

What specific documents are created when mapping a codebase structure?

When mapping a codebase structure, the workflow creates seven structured documents under .planning/codebase/: STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, and CONCERNS.md. These collectively capture the project's current state.

Do I need any dependencies to run the parallel codebase mapping workflow?

No dependencies are required to run the parallel codebase mapping workflow. It independently orchestrates parallel agents to analyze your existing codebase and produce the formal seven-document map under the .planning/codebase/ directory.