Help us improve
Share bugs, ideas, or general feedback.
From sdd
Provides templates and analysis guidance for mapping codebases into specialized documentation. Used by the sdd:code-mapper agent to generate 8 focused codebase documents.
npx claudepluginhub aaronbassett/agent-foundry --plugin sddHow this skill is triggered — by the user, by Claude, or both
Slash command
/sdd:code-mappingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides templates and analysis guidance for generating comprehensive codebase documentation. It supports four focus areas, each producing two specialized documents.
references/focus-guides/arch-analysis.mdreferences/focus-guides/conventions-analysis.mdreferences/focus-guides/security-analysis.mdreferences/focus-guides/tech-analysis.mdreferences/templates/architecture.mdreferences/templates/concerns.mdreferences/templates/conventions.mdreferences/templates/integrations.mdreferences/templates/security.mdreferences/templates/stack.mdreferences/templates/structure.mdreferences/templates/testing.mdGenerates documentation explaining codebase architecture, key components, data flow, and development guidelines. Useful for understanding unfamiliar code, creating onboarding docs, or documenting system architecture.
Orchestrates parallel subagents to map any codebase, creating docs/CODEBASE_MAP.md with architecture, file roles, dependencies, and navigation. Updates incrementally via git or scans.
Scaffolds project documentation (README, ARCHITECTURE, API, CODE_COMMENTS) from templates with placeholders and standards. Use for bootstrapping docs in new or under-documented codebases.
Share bugs, ideas, or general feedback.
This skill provides templates and analysis guidance for generating comprehensive codebase documentation. It supports four focus areas, each producing two specialized documents.
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 |
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
Each generated document MUST:
src/api/auth.py)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 |
references/focus-guides/{focus}-analysis.mdreferences/templates/.sdd/codebase/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 issuesAnalysis 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