write-documentation

Documentation gaps are found by analyzing project structure and configuration options to identify undocumented modules. The skill scans local codebases and checks existing specs to detect missing docs for internal components and project conventions.

To generate documentation matching existing styles, the tool analyzes your current docs and project's CLAUDE.md conventions. New documentation is then created dynamically to align seamlessly with the established structure and formatting.

Yes, you can automatically create documentation for a specific module by triggering the skill with a command like "document the X module". It analyzes the code and generates docs focusing on configuration options and internal specifications.

Local codebase access is required to document internal specifications accurately. The tool relies on local project structure and conventions defined in CLAUDE.md to ensure context consistency and correctly fill knowledge gaps.

The best way to document configuration options and internal specs is to automate gap detection and dynamic doc creation. This ensures all project modules are fully documented and accessible while matching existing documentation styles.

Automated doc generation is limited by its reliance on local codebase access and the project's CLAUDE.md definitions. It cannot document external dependencies or generate specs without existing project structure and conventions for context.