architecture-decision-records

Architecture Decision Records document significant technical choices by capturing context, considered options, final decisions, and consequences. This Skill generates structured ADRs using standard, lightweight, Y-statement, deprecation, or RFC templates to ensure clear, auditable technical decision-making.

ADR lifecycle management tracks records through Proposed, Accepted, Deprecated, and Superseded states. This Skill organizes ADRs within your project directory and maintains a searchable index, ensuring historical context and rationale remain accessible as architectural choices evolve.

RFC-style ADRs suit decisions requiring broader stakeholder review and proposal feedback, while standard ADRs document finalized technical choices. This Skill supports both formats, allowing you to select the appropriate template based on whether a decision needs community input or direct documentation.

Yes, the architecture-decision-records Skill depends on the adr-tools command-line utility to generate, manage, and index Architecture Decision Records within your development environment, providing the underlying file creation and organizational capabilities.

Lightweight ADR templates provide a concise format for documenting technical decisions without extensive overhead. This Skill supports lightweight templates alongside standard, Y-statement, deprecation, and RFC styles, letting you match documentation depth to each decision's significance.

Create an ADR by selecting a template, then document the context driving the technology adoption, the options considered, the final decision, and resulting consequences. This Skill structures the record so future teams understand why TypeScript was chosen and what trade-offs were accepted.