skills.rest
vndee
vndeeCOMMUNITY
Explore all skills by this author →
Website𝕏@DeeHuynh99GitHub

adr

Document architectural decisions with context, rationale, and trade-offs.

3|Updated Mar 22, 2026
Search Tags:#architecture#documentation#adr#governance#trade-offs#decision-record
One-click install
npx skills add https://github.com/vndee/engineering-skills --skill adr-vndee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/vndee/engineering-skills/tree/main/.claude/skills/adr
Command: npx skills add https://github.com/vndee/engineering-skills --skill adr-vndee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decisions about architectures and frameworks are often hard to justify later, leading to relitigations and inconsistency. ADRs capture the context, rationale, and trade-offs behind key technical decisions so future you understands why choices were made.

Core Features & Use Cases

  • Document decision rationale: Record the selected framework, pattern, or tool and the reasons.
  • Track alternatives and trade-offs: Capture explored options and their pros/cons.
  • Support governance and evolution: Provide a traceable history for audits, onboarding, and future changes.

Quick Start

Create ADR-001 with a clear title, status, and date, then fill in Context, Decision, Alternatives Considered, Consequences, and Review Triggers.

Frequently Asked Questions about adr

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

FAQPage Schema
What is the best way to track architecture trade-offs and alternatives considered?▼

Track alternatives and trade-offs by documenting explored options alongside their pros and cons within the decision record. Recording these alternatives ensures future teams understand the evaluated choices and prevents rehashing outdated technical debates.

When do I need to use an architecture decision record for evaluating trade-offs?▼

Structure an architecture decision record using standardized fields like ADR-NNN, Context, Decision, Alternatives Considered, Consequences, and Review Triggers. This format provides a traceable history for audits and onboarding.

When do I need to use an architecture decision record for evaluating trade-offs?▼

Structure an architecture decision record using standardized fields like ADR-NNN, Context, Decision, Alternatives Considered, Consequences, and Review Triggers. This format provides a traceable history for audits and onboarding.

How do I update architecture decisions as project needs change over time?▼

Update architecture decisions by applying versioning and cross-team review to existing decision records. Including Review Triggers in the documentation helps identify when past choices require re-evaluation due to evolving project requirements.

Related Skills

Explore More Software Engineering Skills→
michalvavramichalvavra
16

tech-comparison

Compare technology options using weighted scoring criteria and structured recommendations.

Community
Advanced
e2itse2its
1

factory-adr-management

Manage ADR, FDR, and Divergence Record lifecycles with constitution synchronization and CI gate enforcement.

Community
Advanced
slashwhyslashwhy
5

architectural-documentation

Generate templates for implementation plans, ADRs, API specifications, and migration guides.

Official
Basic
keshavraj936keshavraj936

architecture

Guide architectural decisions with requirements analysis, trade-off evaluation, and ADR documentation.

Community
Advanced