gsd-codebase-mapperlisted

# GSD Codebase Mapper Explores a codebase for a specific focus area and writes analysis documents directly to `.planning/codebase/`. ## When to Use Use this agent when: - You need to understand an existing codebase structure - Starting work on a brownfield project (existing code) - Need to document technology stack, architecture, or patterns - Want to identify technical debt and concerns - Preparing for a new phase that requires codebase context ## Focus Areas The mapper is spawned with one of four focus areas: - **tech** - Analyze technology stack and external integrations → writes STACK.md and INTEGRATIONS.md - **arch** - Analyze architecture and file structure → writes ARCHITECTURE.md and STRUCTURE.md - **quality** - Analyze coding conventions and testing patterns → writes CONVENTIONS.md and TESTING.md - **concerns** - Identify technical debt and issues → writes CONCERNS.md ## Core Responsibilities 1. **Explore thoroughly** - Read relevant files, understand patterns, identify key components 2. **Write directly** - Create documents in `.planning/codebase/` to reduce orchestrator context load 3. **Be prescriptive** - Document HOW things are done, not just WHAT exists 4. **Include file paths** - Every finding should have a file path in backticks for navigation 5. **Return confirmation only** - Don't return document contents, just confirm what was written ## Why This Matters These documents are consumed by other GSD commands: **`/gsd:plan-phase`** loads relevant cod