adr

Automate creation, management, and tracking of architecture decision records in markdown.

1|Updated May 17, 2026
One-click install
npx skills add https://github.com/furedea/agent-harness --skill adr-furedea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/furedea/agent-harness/tree/main/agents/skills/adr
Command: npx skills add https://github.com/furedea/agent-harness --skill adr-furedea

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The adr Skill solves the issue of recording and maintaining architecture decision records (ADRs) by providing a systematic approach to capture decisions, their rationale, and the implications on a project.

Core Features & Use Cases

  • Automated ADR Creation: Generates ADR files for recorded decisions with minimal effort.
  • Decision Record Management: Organizes and tracks decisions through a structured directory and file naming system.
  • Rationale Documentation: Ensures that the 'why' behind decisions is documented alongside the decision itself.

Quick Start

Utilize the adr skill by running 'adr generate' followed by 'adr commit' to document a new architectural decision.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I document architectural decisions automatically in a project?

Architecture decision records (ADRs) capture the 'why' behind a decision alongside its implications, providing a systematic approach to maintaining historical context for project management and code quality.

What is the best way to organize architecture decision records in a directory?

The best way to organize ADRs is by using a structured directory and file naming system that tracks decisions chronologically, ensuring rationale documentation is maintained alongside the decision files.

How do I track the rationale for architectural choices made in my codebase?

You track the rationale for architectural choices by generating markdown ADR files that capture the decision-making process, ensuring the 'why' behind decisions is systematically maintained within your project structure.

Do I need any specific dependencies to start tracking architecture decision records?

No dependencies are required to start tracking architecture decision records. The system operates independently, utilizing markdown files and a structured directory to maintain decision logs.

Can I use markdown for architecture decision records management?

Yes, you can use markdown for architecture decision records management. The system utilizes markdown formatting within a structured directory to capture and organize the decision-making process and its implications.

Why does documenting decisions matter for code quality?

Documenting decisions matters for code quality because it captures the rationale behind structural choices, preventing knowledge loss and ensuring future architectural changes respect the established project constraints.