docs-generate-repo

To generate repository documentation from design specs, this Skill reads module design docs and transforms them into user-facing guides, including architecture overviews and integration sections, automatically.

Automating markdown documentation creation is handled by transforming design docs into structured topic guides, cross-linked architecture overviews, and troubleshooting sections that follow repository documentation standards.

Design doc transformation works by reading configuration and module design docs, then validating word counts and formatting to produce structured, cross-linked topic guides and architecture overviews for the repository.

Yes, generating repository documentation requires design docs stored in .claude/design/design.config.json alongside module design docs, which are parsed to validate output structure, length, and cross-references.

Generating architecture overviews and topic guides produces structured markdown sections containing integration guides, troubleshooting sections, cross-links, and sensible examples validated against formatting standards.

Repository documentation validation fails when generated output does not meet required structure, length, or cross-reference standards, or when input design docs lack sufficient detail for topic guide generation.