gsd-map-codebase

Map codebases into seven structured planning documents under .planning/codebase/.

1|Updated Aug 17, 2025
One-click install
npx skills add https://github.com/DuySeu/StockMind --skill gsd-map-codebase-duyseu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-map-codebase
Source: https://github.com/DuySeu/StockMind/tree/main/.agent/skills/gsd-map-codebase
Command: npx skills add https://github.com/DuySeu/StockMind --skill gsd-map-codebase-duyseu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding, maintenance, and evolution of a codebase often require manual discovery and documentation. This Skill orchestrates parallel gsd-codebase-mapper agents to generate a structured codebase map under .planning/codebase/ for rapid comprehension and planning.

Core Features & Use Cases

  • Parallel mapping: four agents run concurrently to generate seven planning documents: STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, and CONCERNS.md.
  • Brownfield readiness and refresh: suitable before major refactors, during onboarding, or after significant code evolution to keep documentation up to date.
  • Consistent outputs: standardized planning docs that summarize architecture, structure, standards, and risks to accelerate decision-making and planning.

Quick Start

Run the map-codebase workflow to generate the 7 planning 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 automatically map an unfamiliar codebase for onboarding?

Automatically mapping a codebase involves orchestrating four parallel agents to scan the repository and generate seven structured markdown files under .planning/codebase/. These documents detail architecture, stack, integrations, and conventions to accelerate onboarding.

What planning documents are needed for a major codebase refactor?

Essential planning documents for a major refactor include STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, and CONCERNS.md. These seven files provide a comprehensive map of the current codebase state to guide refactoring decisions.

Can I generate architecture documentation for a brownfield project automatically?

Yes, you can generate architecture documentation for brownfield projects by running parallel mapping agents. The agents analyze the existing codebase state and output structured documents like ARCHITECTURE.md and STRUCTURE.md under a dedicated .planning/codebase/ directory.

How does parallel codebase mapping work?

Parallel codebase mapping works by orchestrating four concurrent mapper agents to analyze different aspects of a repository simultaneously. This parallelization generates seven standardized planning documents that summarize architecture, structure, standards, and risks faster than sequential processing.

Do I need to create the .planning/codebase/ directory before mapping?

No, you do not need to manually create the .planning/codebase/ directory before mapping. The mapping workflow automatically creates this directory if absent, orchestrates the parallel agents to write the seven documents, and performs a final commit and verification step.