adr-writer

You can document architecture decisions by creating Architecture Decision Records. This skill automates ADR creation using a predefined template to ensure concise, consistent documentation of repo-level choices and policies.

Automating ADR creation ensures a clear decision trail without documentation bloat. This skill provides workflow automation, handling numbering and validation to efficiently record decisions affecting repository structure or standards.

To generate a new Architecture Decision Record, run the command `npm run adr:new -- "Decision description"`. This triggers the script to automatically populate a concise template with your provided decision context.

You should write an ADR when a decision is made that affects your repository's structure, standards, or policies. It provides a structured format to maintain a clear history of architecture decisions and avoid documentation bloat.

Yes, the ADR writer uses a predefined template for consistency and clarity. Template-based writing ensures all architecture decision records follow a structured format, keeping repository documentation concise and uniform.

Yes, you can integrate this into existing repository maintenance workflows. It provides automation scripts and assets to efficiently create and update ADRs, maintaining your repository's design and structure documentation.