architecture-decision-records

Architecture Decision Records (ADRs) capture the context, rationale, and consequences of significant technical decisions in software development. You need ADRs to maintain clarity, transparency, and continuity across the project lifecycle when making structural choices.

To write an Architecture Decision Record for a new database, use a provided template to structure the context, decision, consequences, pros, and cons. The Skill offers standard, Y-Statement, and lightweight templates to document the rationale effectively.

Yes, you can manage the ADR lifecycle by tracking status changes from proposed to accepted, deprecated, or superseded. This lifecycle management ensures that architectural decisions remain transparent and their historical context is preserved over time.

The best way to structure technical documentation for architectural decisions is using a standardized ADR template. This Skill provides a template library including standard, lightweight, Y-Statement, and deprecation formats to ensure consistent documentation of context and consequences.

Yes, the ADR Skill supports lightweight templates alongside standard, Y-Statement, and deprecation formats. This allows you to document smaller technical decisions with appropriate detail without the overhead of a full architectural record.

An ADR needs to capture context and consequences to ensure clarity and continuity across the project lifecycle. Documenting the rationale behind significant technical decisions prevents knowledge loss and explains why a specific architectural choice was accepted or superseded.