gsd-map-codebase

Analyze a codebase and generate seven planning documents in .planning/codebase/.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/onelee85/my-skills --skill gsd-map-codebase-onelee85
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-map-codebase
Source: https://github.com/onelee85/my-skills/tree/main/gsd-map-codebase
Command: npx skills add https://github.com/onelee85/my-skills --skill gsd-map-codebase-onelee85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze an existing codebase to produce a structured .planning/codebase/ document set using parallel mapper agents.

Core Features & Use Cases

  • Parallel mapper agents write 7 structured documents to .planning/codebase/ covering tech focus, architecture, structure, conventions, testing, and concerns.
  • Orchestrator validates document set, offers refresh or skip, and suggests next steps like /gsd-new-project or /gsd-plan-phase.
  • Useful for brownfield onboarding, pre-refactoring analysis, and ongoing codebase health checks.

Quick Start

Invoke the gsd-map-codebase skill to generate a fresh codebase map and have parallel agents write all seven planning documents to .planning/codebase/.

Frequently Asked Questions about gsd-map-codebase

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

FAQPage Schema
How does parallel codebase mapping work for documentation planning?

Codebase mapping for brownfield projects analyzes an existing codebase using parallel mapper agents to generate structured documentation. It helps developers understand architecture, conventions, and concerns before initiating refactoring or onboarding.

How do I generate a structured codebase map for a brownfield project?

To generate a codebase map, invoke the mapping skill to deploy four parallel agents that analyze your codebase and write seven structured documents to the .planning/codebase/ directory. The orchestrator validates these documents before committing the map.

What documents are generated when mapping codebase structure and architecture?

Mapping a codebase generates seven structured documents covering tech focus, architecture, structure, conventions, testing, and concerns. These files are written to the .planning/codebase/ directory to provide a comprehensive project overview.

Can I use parallel agents to map an existing codebase for refactoring?

Yes, you can use parallel mapper agents to analyze an existing codebase for pre-refactoring analysis. The generated documentation provides a structured health check to inform your refactoring strategy and keep documentation current.

What is the best way to keep codebase documentation up to date?

The best way to maintain codebase documentation is performing periodic health checks using parallel mapping agents. The orchestrator validates existing .planning/codebase/ documents and offers a refresh option to update the seven generated files.

What should I do after generating a codebase map for planning?

After generating a codebase map, the orchestrator suggests next steps like initializing a new project or planning a phase. These downstream actions leverage the generated .planning/codebase/ documents to guide development.