Codebase Mapping Skill
This skill provides templates and analysis guidance for generating comprehensive codebase documentation. It supports four focus areas, each producing two specialized documents.
Focus Area Routing
When invoked, check the focus parameter to determine which templates and analysis guides to use:
| Focus Area |
Templates to Use |
Analysis Guide |
tech |
stack.md, integrations.md |
tech-analysis.md |
arch |
architecture.md, structure.md |
arch-analysis.md |
conventions |
conventions.md, testing.md |
conventions-analysis.md |
security |
security.md, concerns.md |
security-analysis.md |
Output Location
All documents are written to: .sdd/codebase/
Files use UPPERCASE naming: STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, SECURITY.md, CONCERNS.md
Document Quality Requirements
Each generated document MUST:
- Be Actionable: Content should guide future development decisions
- Include File Paths: Reference actual paths in backticks for navigation (e.g.,
src/api/auth.py)
- Be Current: Reflect the actual state of the codebase at time of generation
- Focus on What Executes: Capture only what runs (languages, runtime, frameworks, dependencies)
- Limit Dependencies: Document 5-10 most important dependencies, not every entry
- Specify Versions: Only when compatibility matters
- Use Prescriptive Language: Guide future code generation with clear patterns
Exclusions by Document
Content belongs in specific documents - avoid duplication:
| If Content Is About... |
Put It In... |
NOT In... |
| Languages, frameworks, versions |
STACK.md |
ARCHITECTURE.md |
| External APIs, databases, auth services |
INTEGRATIONS.md |
STACK.md |
| System design, patterns, data flow |
ARCHITECTURE.md |
STRUCTURE.md |
| Directory layout, module boundaries |
STRUCTURE.md |
ARCHITECTURE.md |
| Code style, naming, error handling |
CONVENTIONS.md |
TESTING.md |
| Test strategy, frameworks, patterns |
TESTING.md |
CONVENTIONS.md |
| Auth, authorization, vulnerabilities |
SECURITY.md |
CONCERNS.md |
| Tech debt, risks, TODOs |
CONCERNS.md |
Any other doc |
How to Use This Skill
- Read the focus-specific analysis guide from
references/focus-guides/{focus}-analysis.md
- Load the relevant templates from
references/templates/
- Analyze the codebase following the analysis guide instructions
- Fill templates with discovered information
- Write documents directly to
.sdd/codebase/
- Return confirmation only: file paths + line counts
Template Files
Templates are located in references/templates/:
stack.md - Languages, frameworks, dependenciesintegrations.md - External services, APIs, data storesarchitecture.md - System design, patterns, data flowstructure.md - Directory layout, module boundariesconventions.md - Code style, naming, patternstesting.md - Test strategy, frameworks, patternssecurity.md - Auth, authorization, vulnerabilitiesconcerns.md - Tech debt, risks, known issues
Focus Guides
Analysis guides are located in references/focus-guides/:
tech-analysis.md - How to analyze tech stack and integrationsarch-analysis.md - How to analyze architecture and structureconventions-analysis.md - How to analyze conventions and testingsecurity-analysis.md - How to analyze security and concerns
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: sddcode-mapping3description: Provides templates and analysis guidance for mapping codebases into specialized documentation. Used by the sdd:code-mapper agent to generate 8 focused codebase documents.4---56# Codebase Mapping Skill78This skill provides templates and analysis guidance for generating comprehensive codebase documentation. It supports four focus areas, each producing two specialized documents.910## Focus Area Routing1112When invoked, check the `focus` parameter to determine which templates and analysis guides to use:1314| Focus Area | Templates to Use | Analysis Guide |15|------------|------------------|----------------|16| `tech` | stack.md, integrations.md | tech-analysis.md |17| `arch` | architecture.md, structure.md | arch-analysis.md |18| `conventions` | conventions.md, testing.md | conventions-analysis.md |19| `security` | security.md, concerns.md | security-analysis.md |2021## Output Location2223All documents are written to: `.sdd/codebase/`2425Files use UPPERCASE naming: `STACK.md`, `INTEGRATIONS.md`, `ARCHITECTURE.md`, `STRUCTURE.md`, `CONVENTIONS.md`, `TESTING.md`, `SECURITY.md`, `CONCERNS.md`2627## Document Quality Requirements2829Each generated document MUST:30311. **Be Actionable**: Content should guide future development decisions322. **Include File Paths**: Reference actual paths in backticks for navigation (e.g., `src/api/auth.py`)333. **Be Current**: Reflect the actual state of the codebase at time of generation344. **Focus on What Executes**: Capture only what runs (languages, runtime, frameworks, dependencies)355. **Limit Dependencies**: Document 5-10 most important dependencies, not every entry366. **Specify Versions**: Only when compatibility matters377. **Use Prescriptive Language**: Guide future code generation with clear patterns3839## Exclusions by Document4041Content belongs in specific documents - avoid duplication:4243| If Content Is About... | Put It In... | NOT In... |44|------------------------|--------------|-----------|45| Languages, frameworks, versions | STACK.md | ARCHITECTURE.md |46| External APIs, databases, auth services | INTEGRATIONS.md | STACK.md |47| System design, patterns, data flow | ARCHITECTURE.md | STRUCTURE.md |48| Directory layout, module boundaries | STRUCTURE.md | ARCHITECTURE.md |49| Code style, naming, error handling | CONVENTIONS.md | TESTING.md |50| Test strategy, frameworks, patterns | TESTING.md | CONVENTIONS.md |51| Auth, authorization, vulnerabilities | SECURITY.md | CONCERNS.md |52| Tech debt, risks, TODOs | CONCERNS.md | Any other doc |5354## How to Use This Skill55561. **Read the focus-specific analysis guide** from `references/focus-guides/{focus}-analysis.md`572. **Load the relevant templates** from `references/templates/`583. **Analyze the codebase** following the analysis guide instructions594. **Fill templates** with discovered information605. **Write documents** directly to `.sdd/codebase/`616. **Return confirmation only**: file paths + line counts6263## Template Files6465Templates are located in `references/templates/`:66- `stack.md` - Languages, frameworks, dependencies67- `integrations.md` - External services, APIs, data stores68- `architecture.md` - System design, patterns, data flow69- `structure.md` - Directory layout, module boundaries70- `conventions.md` - Code style, naming, patterns71- `testing.md` - Test strategy, frameworks, patterns72- `security.md` - Auth, authorization, vulnerabilities73- `concerns.md` - Tech debt, risks, known issues7475## Focus Guides7677Analysis guides are located in `references/focus-guides/`:78- `tech-analysis.md` - How to analyze tech stack and integrations79- `arch-analysis.md` - How to analyze architecture and structure80- `conventions-analysis.md` - How to analyze conventions and testing81- `security-analysis.md` - How to analyze security and concerns8283---84> Converted and distributed by [TomeVault](https://tomevault.io/claim/aaronbassett) — claim your Tome and manage your conversions.85<!-- tomevault:4.0:skill_md:2026-04-13 -->
tomevault-io