architecture-decision-records

Document architectural decisions with structured ADR templates and lifecycle states.

4|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Data-Wise/craft --skill architecture-decision-records-data-wise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/Data-Wise/craft/tree/main/skills/docs/architecture-decision-records
Command: npx skills add https://github.com/Data-Wise/craft --skill architecture-decision-records-data-wise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.

Core Features & Use Cases

  • ADR templates that capture context, decision, and consequences for major design decisions.
  • ADR lifecycle including Proposed, Accepted, Deprecated, and Superseded to track evolution.
  • ADR index and management guidelines to link related decisions and maintain traceability.

Quick Start

Create a new ADR in docs/adr using the template and begin the review workflow.

Frequently Asked Questions about architecture-decision-records

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are Architecture Decision Records and when do I need to document them?

Architecture Decision Records (ADRs) document significant technical decisions by capturing context, decisions, and consequences. You need ADRs when selecting major frameworks, defining tech stacks, or establishing governance for design trade-offs across engineering projects.

How do I write an Architecture Decision Record using a structured template?

To write an Architecture Decision Record, create a new file in your docs directory using a structured ADR template. Fill in the context, decision, and consequences sections, then initiate the review workflow to ensure collaborative decision making and traceability.

How do I track the lifecycle of an architectural decision from proposal to deprecation?

You can track an architectural decision lifecycle using statuses like Proposed, Accepted, Deprecated, and Superseded. Maintaining an ADR index links related decisions and preserves traceability as your technical choices evolve across projects.

Does adr-tools work for automating Architecture Decision Record versioning and management?

Yes, adr-tools provides automation tips for managing Architecture Decision Records, ensuring proper versioning and traceability. It supports the review guidelines and indexing needed to maintain collaborative decision making within engineering teams.

What is the best way to govern architectural decisions across multiple engineering projects?

The best way to govern architectural decisions is implementing standardized ADR templates and an ADR index. This establishes a formal review workflow and lifecycle tracking, ensuring design trade-offs and framework choices remain traceable across projects.