gsd-map-codebase

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an unfamiliar or evolving codebase into a structured, shareable map so teams can understand the project before planning changes.

Core Features & Use Cases

  • Uses parallel mapper agents to inspect different parts of the repository at the same time.
  • Produces seven standardized documents in .planning/codebase/ covering stack, architecture, structure, conventions, testing, integrations, and concerns.
  • Helps with brownfield onboarding, subsystem discovery, pre-refactor analysis, and refreshing stale project state after major changes.

Quick Start

Ask the assistant to map the current codebase, or a specific area like api or auth, and write the planning documents into .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 map an unfamiliar codebase for brownfield onboarding?

Codebase mapping for brownfield onboarding analyzes an existing repository and produces seven structured planning documents covering stack, architecture, structure, conventions, testing, integrations, and concerns. It uses parallel agents to inspect different parts of the repository simultaneously.

What's the best way to generate architecture and planning docs before a refactor?

Generating planning docs for pre-refactor assessment requires analyzing the codebase to output structured architecture and subsystem documents. This approach standardizes project state documentation into a .planning/codebase/ directory for team review.

Can I map a specific subsystem like an api or auth module instead of the entire repository?

Mapping a specific subsystem like api or auth targets only that area of the codebase while still producing the standardized planning documents. This targeted discovery process helps teams understand isolated modules before planning changes.

What planning documents are produced when analyzing a codebase?

Analyzing a codebase produces seven standardized planning documents in the .planning/codebase/ directory covering stack, architecture, structure, conventions, testing, integrations, and concerns, providing a complete and validated project map.

How do I refresh stale project state documentation after major codebase changes?

Refreshing stale project state after major changes involves re-running codebase mapping to regenerate the seven planning documents. This ensures the .planning/codebase/ directory reflects the current architecture, integrations, and conventions accurately.

Does codebase mapping work for large repositories with complex architecture?

Codebase mapping for large repositories uses parallel mapper agents to inspect different areas simultaneously, making it suitable for complex architecture. The confirmation-only orchestration validates that the .planning/codebase/ directory is complete.