adr-writer

To document architectural decisions for databases and frameworks, you can generate MADR-style ADRs that capture context, options, and rationale. This ensures consistent documentation standards and traceability for future maintenance.

An architecture decision record (ADR) captures the rationale, context, and trade-offs behind meaningful software architecture choices. You need an ADR when making non-trivial decisions across databases, frameworks, and deployment patterns to ensure reasoning is documented.

Automatic ADR indexing works by writing MADR-style decision records into docs/architecture/adr/NNNN-decision-slug.md files and automatically updating the ADR index when new records are added, maintaining an organized directory with proper numbering and linking.

The best way to maintain an organized ADR directory is to automate creation and indexing of architecture decision records. This approach writes files with proper numbering and automatically updates the index when new ADRs are added.

Yes, you can use MADR-style templates for deployment pattern decisions. The ADR writer supports non-trivial decisions across deployment patterns, capturing context, options, and rationale while ensuring consistent documentation standards.