lets-document

Automating system documentation requires analyzing the codebase for structural truth and conducting user interviews for context. This Skill generates markdown files detailing architecture and business processes directly in your repository.

Generating architectural overviews without manual user input is possible for structural details, but user interviews are required to capture rationale and business process context not directly available in the code.

Documenting business processes alongside software architecture is best achieved by combining automated code analysis with targeted user interviews. This ensures both structural accuracy and human rationale are captured in markdown files.

In-repo documentation generation works by creating and maintaining markdown files within your repository for version control. It uses the codebase as the source of truth, supplementing existing documentation with architectural and functional details.

Documenting a specific subsystem within a larger software system involves running a targeted command with the subsystem topic. This generates focused markdown documentation detailing that specific feature's architecture and functionality.