Sign in
Explore
Prompts · PromptEveryday codingReviewed

gsd/map-codebase

Analyses the codebase with parallel mapper agents and writes documents to .planning/codebase/.

Kind
Prompt
Works with
Claude Code, Gemini / Antigravity
Source
gsd-build/get-shit-done @ bdcaab2c752d
Path
commands/gsd/map-codebase.md
License
MIT
Jobs
Documentation
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
<objective>
Analyze existing codebase using parallel gsd-codebase-mapper agents to produce structured codebase documents.

Each mapper agent explores a focus area and **writes documents directly** to `.planning/codebase/`. The orchestrator only receives confirmations, keeping context usage minimal.

Output: .planning/codebase/ folder with 7 structured documents about the codebase state.
</objective>

<execution_context>
@~/.claude/get-shit-done/workflows/map-codebase.md
</execution_context>

<flags>
- **--fast**: Lightweight scan mode — spawns one mapper agent instead of four. Accepts an optional `--focus` value: `tech`, `arch`, `quality`, `concerns`, or `tech+arch` (default). Faster and lower-context than the full map.
- **--query**: Codebase intelligence query mode. Sub-commands: `query <term>`, `status`, `diff`, `refresh`. Requires intel to be enabled in config (`intel.enabled: true`). Runs inline for query/status/diff; spawns an agent for refresh.
- **(no flag)**: Full parallel map — spawns 4 mapper agents to produce all 7 codebase documents.
</flags>

<context>
Arguments: $ARGUMENTS

Parse the first token of $ARGUMENTS:
…