gsd-map-codebase

Generate structured codebase mapping documents with parallel mapper agents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of onboarding to an unfamiliar repository or recovering lost architectural knowledge by generating a structured, up-to-date codebase map.

Core Features & Use Cases

  • Parallel codebase mapping: Spawns multiple mapper agents to scan distinct areas (tech, architecture, quality, concerns) and write results directly into a planning folder.
  • Structured deliverables: Produces a consistent set of codebase documents (7 total) to support planning, refactoring, and review workflows.
  • Refresh and query modes: Supports fast scans and intelligence-oriented queries (status/diff/refresh) to keep the map current.

Quick Start

Run gsd-map-codebase to create .planning/codebase/ documents for your current repository state.

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 unfamiliar codebase to speed up onboarding?

To generate codebase documentation for onboarding, you can run a codebase mapping tool that spawns parallel agents to scan repository areas like architecture and quality, writing structured documents directly into a planning folder.

What is the best way to map an existing repository architecture without manual review?

Mapping repository architecture automatically is best handled by parallel mapper agents that scan distinct technical areas and generate a consistent set of structured codebase documents for planning and review.

Can I refresh codebase mapping documents after significant changes to a brownfield project?

Yes, you can refresh codebase mapping documents after significant changes using intelligence-oriented query modes like status, diff, and refresh to keep the existing repository map current.

Does codebase mapping support targeted scans for specific focus areas within a repository?

Yes, codebase mapping supports optional focus areas, allowing you to target specific parts of a repository during full, fast, or intel-driven query workflows to generate localized planning artifacts.

How many structured documents are produced when analyzing a codebase for architecture discovery?

Analyzing a codebase for architecture discovery produces a consistent set of seven structured documents that cover technical, architectural, quality, and concern areas to support refactoring workflows.

What limitations exist when using parallel agents for repository analysis?

Using parallel agents for repository analysis writes documents directly from the mapper agents, meaning outputs are constrained to the defined planning folder structure and require intel-driven refresh workflows to stay current.