gsd-map-codebase

Coordinate four parallel agents to generate seven codebase planning documents.

Updated Apr 22, 2026

Search Tags:#automation #parallel-agents #planning-docs #architecture-mapping #codebase-documentation #map-codebase

Ready to run

npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-map-codebase-hadpadrahul

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-map-codebase
Source: https://github.com/hadpadrahul/school-erp/tree/main/.codex/skills/gsd-map-codebase
Command: npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-map-codebase-hadpadrahul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of structured codebase maps by coordinating multiple mapper agents, generating seven predefined documents under .planning/codebase/. This reduces manual overhead and ensures consistent, up-to-date architecture documentation.

Core Features & Use Cases

Parallel 4-agent mapping to generate seven documents in .planning/codebase/.
Non-intrusive orchestration: agents write documents directly; the orchestrator only confirms completion.
Use Case: Brownfield projects before initialization; refresh after major changes; onboarding to unfamiliar codebase.

Quick Start

Invoke the map-codebase workflow to generate the seven .planning/codebase/ documents for the current repository.

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 codebase architecture into planning documents?▼

This skill automates codebase mapping by orchestrating four parallel agents that write seven structured architecture and convention documents directly into the .planning/codebase/ directory.

What is the best way to document an unfamiliar brownfield codebase for onboarding?▼

The best way to document a brownfield codebase is orchestrating parallel mapper agents to generate structured planning documents, capturing current architecture, conventions, and concerns non-intrusively without manual overhead.

How do parallel agents generate codebase documentation?▼

Parallel agents generate codebase documentation through non-intrusive orchestration, where four mapper agents independently write seven predefined documents under .planning/codebase/ before the orchestrator validates completion.

Can I refresh codebase mapping documents after major architectural changes?▼

Yes, you can refresh codebase mapping documents after major changes by re-invoking the parallel agent workflow, which overwrites the .planning/codebase/ files with updated architecture, structure, and test mappings.

Do I need an existing .planning/STATE.md file to map a codebase?▼

You do not need an existing .planning/STATE.md file to map a codebase; the workflow loads state from STATE.md when present for continuity, but functions independently for fresh repository initialization.

What are the limitations of using automated agents for codebase architecture mapping?▼

A limitation of automated codebase architecture mapping is that the orchestrator only confirms completion without directly writing documents, meaning agents must autonomously capture all structural conventions and concerns accurately.