document-generate

You can generate missing documentation from scratch by providing feature or module context; the skill outputs complete Markdown docs covering purpose, usage, edge cases, and decision logs using project context and tooling.

Diataxis structures documentation into four types: tutorials, how-to guides, references, and explanations, ensuring comprehensive coverage of learning, doing, information, and understanding for a feature or project.

Yes, you can auto-generate Markdown reference docs for an entire project by invoking the skill standalone or via /document-release when coverage gaps are detected, producing complete structured Markdown files.

Generating tutorials and how-to guides relies on project context and tooling including Bash, Read, Write, and Edit to read source code and write complete Markdown documentation files.

The best way to fill documentation coverage gaps is invoking /document-release, which detects missing docs and generates complete Diataxis-structured Markdown covering purpose, scope, usage, and edge cases.

Automated documentation generation may not suit contexts lacking sufficient project context or tooling access, as producing complete Markdown docs covering edge cases and decision logs requires reading and editing project files.