Architecture Decision Records
Create and maintain architecture decision records (ADRs) using established conventions, templates, and a built-in validator. The skill guides you through prospective and retrospective record creation, enforces quality standards like one decision per record and credible alternatives, and helps manage decision lifecycles with status tracking and supersession links. Use it to build a durable, reviewable record of why architecturally significant choices were made.
Architecture Decision Records helps you document and track architectural decisions with structured templates, validation, and supersession tracking.
AI-generated summary based on this skill's SKILL.md
Install
dirnbauer/webconsulting-skills/architecture-decision-records · repository language: Shell
git clone https://github.com/dirnbauer/webconsulting-skills
cp -r webconsulting-skills ~/.claude/skills/architecture-decision-recordsgenerated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
npx skillfed install dirnbauer/webconsulting-skills/architecture-decision-recordsFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I record architectural decisions?
Architecture Decision Records helps you document and track architectural decisions made during software design. The skill guides you through creating structured records using established conventions and templates, capturing the decision, its context, rationale, and alternatives. Each ADR follows a standardized format to ensure consistency across your project and team.
What is an ADR template for software projects?
Architecture Decision Records provides a built-in template that enforces quality standards for your decision documentation. The template ensures one decision per record, includes credible alternatives, and captures the decision's status and rationale. This standardized approach enables team alignment on architectural direction and creates a searchable, reviewable history of why choices were made.
How can I track architecture decisions over time?
Architecture Decision Records manages decision lifecycles with status tracking and supersession links. The skill lets you record both prospective decisions (before implementation) and retrospective ones (after the fact), maintaining a durable record that shows how architectural choices evolved. This enables you to maintain a searchable history and understand the reasoning behind each decision.
What are ADR best practices?
Architecture Decision Records enforces best practices through its built-in validator and guidance. Key practices include documenting one decision per record, considering credible alternatives, capturing clear rationale, and tracking decision status over time. The skill helps establish a standardized format across your team, enabling better collaboration and ensuring architectural decisions are properly documented and justified.
How does Architecture Decision Records help teams?
Architecture Decision Records enables team alignment by creating a structured, standardized record of design choices and their rationale. Teams use it to build a shared understanding of architectural direction, maintain searchable documentation of why decisions were made, and enforce quality standards through validation. This creates a durable reference that supports both current projects and future onboarding.