adr-writing

To document architectural decisions using the MADR template, this Skill captures context, decision drivers, options considered, and consequences while automatically generating proper YAML frontmatter and applying a Definition of Done checklist for systematic completeness.

The best way to ensure ADR completeness and consistent file naming is to apply a Definition of Done checklist that identifies gaps and automates the assignment of sequential, zero-padded numbers to ADR files.

Automated ADR numbering works by retrieving the next sequential, zero-padded number for each new Architectural Decision Record, ensuring consistent organization and proper file naming conventions across your documentation repository.

Yes, you can capture architectural choices made during project meetings immediately by drafting a formal ADR on the spot, systematically recording the context, decision drivers, options considered, and consequences.

An Architectural Decision Record (ADR) is a formal document that captures significant architectural choices, including context and consequences. You need an ADR whenever a significant architectural choice is made during a project to ensure systematic documentation.

Generating ADRs with a Definition of Done checklist is limited to the standard MADR format structure, meaning it enforces specific YAML frontmatter and file naming conventions rather than supporting fully custom or unstructured architectural documentation formats.