docs

You can automatically generate technical documentation and ADRs by providing a plain language feature description to the docs skill, which then applies structured templates and validates required sections. The output is formatted and saved to the docs/ directory.

An ADR (Architecture Decision Record) documents significant architectural decisions and their context. You need to generate an ADR when making product development choices that require a traceable, structured record for future reference and team alignment.

To create consistent documentation templates, the docs skill applies standardized templates for technical documents, ADRs, and API docs. It enforces structured output and validates required sections to ensure uniform formatting across all generated files.

Yes, the docs skill supports generating release notes and API documentation alongside ADRs. Its workflow applies to product development, architecture decisions, and feature explanations, producing consistent templates for various document types.

No specific dependencies or environment components are required. The docs skill operates independently to process your feature descriptions and save the generated, validated documentation directly into your project's docs/ directory.

The best way to maintain a living documentation system is to automate generation from feature descriptions into the docs/ directory. This approach ensures consistent formatting, validates required sections, and keeps technical docs and ADRs easily integrated and up to date.