gsd-map-codebase

Generate seven structured .planning/codebase/ documents via parallel mapper agents.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-map-codebase-pear-commerce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-map-codebase
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/gsd-map-codebase
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-map-codebase-pear-commerce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually exploring and documenting an existing codebase is time-consuming and prone to oversight, especially when onboarding to a new project, preparing for refactoring, or initializing a new GSD project on a brownfield codebase.

Core Features & Use Cases

  • Parallel Mapper Agents: Spawns 4 specialized agents to explore different focus areas (tech stack, architecture, conventions, technical concerns) in parallel, minimizing context overhead.
  • Structured Documentation Generation: Automatically produces 7 standardized .planning/codebase/ documents covering all critical aspects of the codebase for planning and reference.
  • Use Case: Before starting a new GSD project on an existing e-commerce codebase, run this skill to instantly generate a complete map of the tech stack, integrations, and architectural patterns without manual exploration.

Quick Start

Invoke the gsd-map-codebase skill to analyze your current codebase and generate the full set of .planning/codebase/ planning 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 automate codebase mapping for developer onboarding and project planning?

Automate codebase mapping by spawning parallel agents to explore your codebase and generate structured technical documentation covering the tech stack, architecture, conventions, and concerns. This eliminates manual exploration overhead for project planning and developer onboarding.

What is the best way to generate technical documentation for an unfamiliar codebase?

The best way to generate technical documentation for an unfamiliar codebase is using parallel mapper agents that analyze focus areas like testing and architecture in parallel, producing 7 standardized .planning/codebase/ documents to accelerate onboarding.

Can I use parallel agents to analyze a brownfield codebase before refactoring?

Yes, you can use parallel agents to analyze a brownfield codebase before refactoring. This skill supports post-change codebase refreshes and pre-refactoring analysis by evaluating technical concerns and generating structured planning documents.

How does parallel codebase analysis reduce context usage during project initialization?

Parallel codebase analysis reduces context usage by spawning 4 specialized agents to explore different focus areas simultaneously rather than loading the entire codebase into a single context, yielding structured planning documents with minimal overhead.

Do I need any dependencies to run codebase mapping for technical stack documentation?

No dependencies are required to run codebase mapping for technical stack documentation. The skill operates independently to analyze your codebase and generate the 7 .planning/codebase/ documents covering technical stack, integrations, and architectural patterns.

When should I refresh codebase mapping documents after changes?

You should refresh codebase mapping documents after significant changes to your codebase to ensure your technical documentation stays current. Running a post-change codebase refresh updates the 7 structured .planning/codebase/ documents for accurate project planning.