adr

Create, review, and update Architecture Decision Records with status lifecycle management.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/controlaltnerd/arc --skill adr-controlaltnerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/controlaltnerd/arc/tree/main/.github/skills/adr
Command: npx skills add https://github.com/controlaltnerd/arc --skill adr-controlaltnerd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of documenting significant technical decisions, ensuring clarity, traceability, and a shared understanding within a project.

Core Features & Use Cases

  • Create ADRs: Generate new Architecture Decision Records with auto-populated fields based on context.
  • Review ADRs: Quickly find and understand past architectural choices.
  • Update Status: Manage the lifecycle of decisions from Proposed to Accepted or Rejected.
  • Use Case: When your team decides on a new database technology, use this Skill to create an ADR that captures the context, rationale, alternatives considered, and the final decision.

Quick Start

Use the adr skill to create a new ADR for the decision on using SQLite for data storage.

Frequently Asked Questions about adr

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

FAQPage Schema
What is an Architecture Decision Record and when do I need to document technical decisions?

An Architecture Decision Record (ADR) documents significant technical decisions, capturing context, rationale, alternatives, and consequences. You need ADRs to ensure traceability and shared understanding within a project's technical governance.

How do I create a new Architecture Decision Record for a database technology selection?

Create an Architecture Decision Record by providing context such as the database technology chosen. The skill auto-populates fields to capture the architectural choice, alternatives considered, and the final decision status.

Can I update the status of an Architecture Decision Record from Proposed to Accepted?

Yes, you can update the status of an Architecture Decision Record throughout its lifecycle. The skill manages the progression of decisions from Proposed to Accepted or Rejected for technical governance.

What's the best way to review past architectural choices across a software engineering project?

Review past architectural choices by using the skill to quickly find and understand previous Architecture Decision Records. This facilitates structured documentation for technical governance and knowledge sharing.

Does architecture documentation work without dependencies for technical decision-making processes?

Yes, architecture documentation operates without dependencies. The skill independently manages the creation, review, and updating of Architecture Decision Records for technical decision-making processes.