adr

Capture and standardize architecture decision records in markdown.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/skylarsabo/code-ops --skill adr-skylarsabo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/skylarsabo/code-ops/tree/main/plugins/code-ops-suite/skills/adr
Command: npx skills add https://github.com/skylarsabo/code-ops --skill adr-skylarsabo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill addresses the issue of unclear and difficult-to-reverse architecture decisions within codebases, providing a standardized process for capturing and documenting such decisions for future reference and to aid new contributors.

Core Features & Use Cases

  • Backfill existing decisions: Mined from code and existing documentation, presenting past architecture choices with their context, options, and reasoning.
  • Author new decisions: Facilitate writing ADRs for current decisions in progress, ensuring documentation is thorough and provides rationale.
  • Maintain documentation: ADRs are maintained in a standardized directory with indexing for easy navigation.
  • Proven decision process: Ensures every architectural decision is backed by evidence and weighed options.

Quick Start

Start a new ADR to document the reasoning behind an architecture decision using /code-ops-suite:adr --new.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I document architecture decisions in a standardized markdown format?

Architecture decision records are captured using standardized markdown files that enforce decision-making criteria around cost, context, and trade-offs. They are maintained in an indexed directory for easy navigation and future reference.

What is the best way to backfill past architecture decisions from existing code?

Past architecture decisions can be backfilled by mining existing code and documentation to present historical choices alongside their original context, options, and reasoning, aiding new contributors in understanding the codebase.

When do I need architecture decision records for my codebase?

You need architecture decision records when managing and scaling large codebases to prevent unclear and difficult-to-reverse architectural choices. They ensure every decision is backed by evidence and weighed options for future reference.

How do I start a new architecture decision record for a current software project?

You can start a new architecture decision record by initiating a new ADR entry to document the rationale for a decision in progress. This ensures documentation is thorough and captures the reasoning behind current architecture choices.

Does this architecture decision process work for managing large codebases?

Yes, this architecture decision process is specifically aimed at software engineers managing and scaling large codebases. It provides a standardized process for capturing and documenting decisions to aid new contributors and prevent irreversible mistakes.