adr-write

You can automate Architecture Decision Record creation by using a skill that generates structured ADR documents with sections for context, decision drivers, alternatives, and consequences. This streamlines documenting technical decisions in software development.

An Architecture Decision Record (ADR) is a document capturing significant architectural or technical decisions. You need an ADR when you want to record the context, alternatives, and consequences of a decision to maintain clear documentation in software projects.

To document alternatives and consequences in an ADR, you enumerate alternatives with their pros and cons, then articulate the positive, negative, and neutral impacts. This ensures all decision drivers and outcomes are clearly recorded.

Yes, you can use the Michael Nygard template for automated decision documentation. The skill simplifies ADR generation using this specific template structure, automatically including context, decision drivers, and constraints.

You can manage the ADR status lifecycle and automate number assignment by using a document generation skill. It tracks the status of architecture decisions and assigns sequential numbers to new records automatically.

The best way to track architectural decisions without manual formatting is to automate ADR creation. This approach structures your decision records automatically, covering context, alternatives, and consequences while reducing documentation complexity.