adr

Name: adr
Availability: InStock
Author: ebijun1007

Document cross-cutting architectural decisions in structured ADR files.

Updated Aug 27, 2026

Search Tags:#planning #architecture #documentation #adr #rationale #decision-record

Ready to run

npx skills add https://github.com/ebijun1007/vibe-coding --skill adr-ebijun1007

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/ebijun1007/vibe-coding/tree/main/.claude/skills/adr
Command: npx skills add https://github.com/ebijun1007/vibe-coding --skill adr-ebijun1007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADRs store cross-cutting architectural decisions to prevent repeating debates and inconsistent choices over time.

Core Features & Use Cases

Create and maintain Architecture Decision Records for decisions affecting multiple modules or teams.
Track status (proposed, accepted, superseded, deprecated) and relate ADRs to plans/issues to preserve a decision history.
Reference ADRs to guide future planning and avoid rework.

Quick Start

Create a new ADR file under .claude/decisions/ADR-XXX-<short-title>.md documenting the decision and its rationale.

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 prevent repeating debates later?▼

To document architectural decisions, create structured Architecture Decision Records that capture the rationale, alternatives, and related plans for cross-cutting choices affecting multiple modules, ensuring future teams avoid rework.

What is an Architecture Decision Record and when should I create one?▼

An Architecture Decision Record is a structured file that captures cross-cutting plan-time decisions affecting multiple modules or systemic constraints. You should create one when making architectural choices that impact multiple teams or tools.

How do I track the status of architectural decisions like accepted or superseded?▼

Track architectural decision status using structured frontmatter that records proposed, accepted, superseded, or deprecated states. This maintains a persistent decision history and links related plans to prevent inconsistent choices.

What is the best way to structure an Architecture Decision Record file?▼

The best way to structure an Architecture Decision Record file is using frontmatter with id, title, status, date, supersedes, superseded_by, and related_plans fields, stored persistently under a dedicated decisions directory.

Does documenting architecture rationale work for decisions affecting multiple modules?▼

Documenting architecture rationale is specifically designed for cross-cutting decisions affecting multiple modules, tools, or systemic constraints. It records alternatives and related plans to preserve context and guide future planning.

Why do teams repeat architectural debates six months later and how to avoid it?▼

Teams repeat architectural debates because previous rationale and alternatives are not documented. Avoid this by maintaining a persistent history of Architecture Decision Records that capture status changes and link to related plans.