adr

Record and manage architectural decision documents in a Markdown repository.

2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/dd-xiaozhi/dev-agent-flow --skill adr-dd-xiaozhi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/dd-xiaozhi/dev-agent-flow/tree/main/.claude/skills/adr
Command: npx skills add https://github.com/dd-xiaozhi/dev-agent-flow --skill adr-dd-xiaozhi

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the problem of knowledge loss in software development by providing a structured way to document the "why" behind critical architectural decisions, ensuring that future maintainers understand the context and trade-offs of the current system.

Core Features & Use Cases

  • Decision Tracking: Provides a standardized template for recording architectural decisions, including context, decision, and consequences.
  • Conflict Resolution: Facilitates the comparison of multiple candidate solutions for complex architectural problems using a weighted scoring approach.
  • Lifecycle Management: Supports the evolution of architecture by allowing decisions to be superseded by newer ones, maintaining a clear audit trail of system changes.

Quick Start

Use the adr skill to create a new architectural decision record for the proposed database migration by running the provided python script with the new decision title.

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 to track technical context?

Document architectural decisions using a standardized Markdown template to record context, decisions, and consequences, ensuring future maintainers understand system trade-offs and technical transparency.

What is the best way to compare candidate solutions for complex architectural problems?

Compare candidate solutions for architectural problems using a weighted scoring approach within decision documents, facilitating conflict resolution and providing a clear evaluation of multiple options.

How do I manage the lifecycle of architecture decisions when they change?

Manage architecture decision lifecycle by allowing older decisions to be superseded by newer ones, maintaining a clear audit trail of system changes and tracking status evolution automatically.

When do I need to create architectural decision records in software development?

Create architectural decision records when making critical system design changes, technology stack selections, or establishing global architectural conventions to prevent knowledge loss across the development team.

Does this architectural decision tracking require a specific repository layout?

Yes, this architectural decision tracking requires a structured Markdown-based repository layout to provide automated indexing and status tracking for decision evolution.

How do I create a new architectural decision record for a proposed system change?

Create a new architectural decision record by running the provided Python script with the new decision title, generating a standardized Markdown document for tracking the proposed change.