gad:map-codebase

Map a codebase to planning documentation using the GAD workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map an existing codebase to planning documentation, enabling standardized migration from legacy RepoPlanner alias to current GAD-based planning docs.

Core Features & Use Cases

  • Canonical migration path from rp-* mappings to gad: maps a codebase to planning docs within vendor/get-anything-done/skills.
  • Enables consistent documentation generation across multiple modules and packages.
  • Use Case: When you rehost or refactor a repo, generate a unified planning doc to guide teams.

Quick Start

Run the gad:map-codebase skill to generate planning docs for your repository.

Frequently Asked Questions about gad:map-codebase

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

FAQPage Schema
How do I map an existing codebase to planning documentation?

To map an existing codebase to planning documentation, run the gad:map-codebase skill to generate unified planning docs. This process uses the GAD workflow to create standardized documentation across multiple modules and packages.

What is the best way to migrate legacy rp-* mappings to current planning docs?

The canonical migration path from legacy rp-* mappings to current GAD-based planning docs is achieved by mapping the codebase to planning documentation within the vendor/get-anything-done/skills directory using the GAD workflow.

When do I need to generate unified planning documentation for a repository?

You need to generate unified planning documentation when you rehost or refactor a repository, ensuring teams have consistent guidance across modules and packages during the migration or refactoring process.

How does the GAD workflow generate planning documentation for modern repositories?

The GAD workflow generates planning documentation by implementing its canonical methodology via the gad CLI, specifically running the snapshot command with a project ID to map the codebase structure into standardized docs.

Do I need the gad CLI to map a codebase to planning docs?

Yes, mapping a codebase to planning docs requires the gad CLI. The skill implements the canonical methodology by executing the gad.cjs snapshot command with a specified project ID to generate the documentation.

Can I generate consistent documentation across multiple modules and packages in one run?

Yes, mapping a codebase to planning documentation enables consistent documentation generation across multiple modules and packages, providing a unified planning doc to guide teams through repository refactoring or rehosting.