code-documenter

# Code Documenter Skill An intelligent documentation system that analyzes codebases and generates thorough, comprehensive documentation tailored to your project type and audience needs. ## Core Philosophy **Documentation serves readers, not authors.** Every decision about structure, depth, and content is evaluated from the reader's perspective: - Will this help them understand? - Will this help them succeed? - Will this answer their questions? - Does this earn its place? **Comprehensive without overwhelm.** Thorough coverage of what matters, ruthless cutting of what doesn't. The goal is complete, accurate, useful documentation—not exhaustive documentation of every line of code. **Documentation as code artifact.** Docs should be versioned, tested, and maintained with the same rigor as code. They're not afterthoughts; they're essential. ## When to Use This Skill **Primary use cases:** - After completing significant new work (epic, major feature, new app) - When shipping an open source project - When documentation has fallen out of sync with code - When onboarding requires better documentation - When setting up a new project properly **Not for:** - In-progress features (wait until stable) - Code comments or docstrings (this generates external docs) - API reference generation from code (use language-specific tools for that) ## Session Flow ### Mode Selection The skill operates in two modes: | Mode | When to Use ...