document-feature

Feature documentation generation applies Good Docs templates to create consistent Markdown files. The Skill generates a structured feature doc at /docs/features/[feature-name].md with Overview, Architecture, API Reference, How-To Guides, Technical Decisions, Testing sections, Mermaid diagrams, and real code samples pulled from your repository.

Yes. The Skill embeds Mermaid diagrams for architecture visualization and automatically extracts real code examples from your codebase into the generated documentation, eliminating manual code copying and keeping examples synchronized with your implementation.

Generated feature documentation includes Overview, Architecture, API Reference, How-To Guides, Technical Decisions with ADR links, Testing guidance, and Related Documentation sections, all formatted as Markdown with diagrams and code samples for completeness.

ADRs are optional but recommended. The Skill links to related Architecture Decision Records in the Technical Decisions section, helping readers understand the rationale behind feature design choices without requiring pre-existing documentation.

Template-driven documentation generation ensures consistency across features. By pulling code examples directly from your repository, the Skill reduces drift between docs and implementation, though you regenerate docs when features significantly change.

The Skill uses Good Docs templates as its standard structure: Overview, Architecture, API, How-To, ADRs, Testing, and Related Documentation. While the template sections are fixed, you can adapt content within each section post-generation to match your team's voice and requirements.