adr

Generate structured Architecture Decision Records with consistent sections.

6|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/wesleyosantos91/multi-agents --skill adr-wesleyosantos91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/wesleyosantos91/multi-agents/tree/main/devin/.devin/skills/adr
Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill adr-wesleyosantos91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of undocumented architectural reasoning by guiding consistent creation of Architecture Decision Records (ADRs) for system changes.

Core Features & Use Cases

  • Creates a new ADR on demand: Triggers tech-writer to produce an ADR with the right structure and required sections.
  • Enforces a consistent ADR format: Standardizes Status, Context, Decision, Consequences, and Alternatives to improve traceability.
  • Supports organized storage: Saves ADRs to the expected docs/architecture/adr/ path using sequential numbering.

Quick Start

Use the adr skill to create a new ADR for your next architecture decision.

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 one?

An Architecture Decision Record (ADR) documents the rationale for a software architecture change. You need an ADR when teams require traceable context, decision details, and consequences for system design modifications across projects.

How do I generate an Architecture Decision Record for my software project?

To generate an Architecture Decision Record, provide your decision details as input arguments. The system creates a structured document with Status, Context, Decision, Consequences, and Alternatives sections for your architecture planning.

What format and sections should an Architecture Decision Record include?

An Architecture Decision Record should include Status, Context, Decision, Consequences, and Alternatives sections. This standardized format ensures consistent documentation and improves the traceability of architectural reasoning across your project.

Where should Architecture Decision Records be saved in a repository?

Architecture Decision Records should be saved under the docs/architecture/adr/ directory path. This organized storage approach uses sequential numbering to maintain chronological order and historical traceability of design changes.

Can I use ADRs for documenting any software architecture changes?

Yes, you can use Architecture Decision Records for software architecture planning across projects. They apply whenever your team needs structured documentation and traceable rationale for system design changes or modifications.