documentation-and-adrs

To create an architecture decision record, use the skill to capture the rationale behind significant technical database decisions. It provides structured ADR templates to ensure architectural decisions are consistently documented for future reference.

The best way to maintain a README and changelog is using structured documentation guidelines. This approach provides templates for clear README files and ensures proper tracking of feature additions, fixes, and changes in your changelog.

You need architecture decision records when you want to capture the rationale behind significant technical decisions. They provide a structured approach to manage documentation, ensuring clarity and consistency for future reference within your codebase.

Yes, AI agents can use these documentation guidelines to understand project conventions. The skill assists agents by providing structured ADRs and best practices for inline and API documentation to facilitate knowledge sharing.

No, this skill requires no dependencies to manage documentation. It operates independently to provide templates for READMEs and changelogs, ensuring consistent documentation practices without external setup.