adr

Generate Architecture Decision Records with context, alternatives, and approvers.

49|12|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/DavidROliverBA/ArchitectKB --skill adr-davidroliverba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/DavidROliverBA/ArchitectKB/tree/main/.claude/skills/adr
Command: npx skills add https://github.com/DavidROliverBA/ArchitectKB --skill adr-davidroliverba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of Architecture Decision Records (ADRs), ensuring that critical architectural choices are properly documented, justified, and tracked according to organizational standards.

Core Features & Use Cases

  • Guided ADR Creation: Walks users through the process of defining ADR context, alternatives, decisions, and consequences.
  • Approver Identification: Helps identify and list required approvers based on subject areas and organizational policies.
  • Use Case: When deciding on a new database technology, this Skill will guide you through documenting the problem, evaluating alternatives like SQL vs. NoSQL, capturing the final decision, and identifying the necessary approvers from Security, Data, and Engineering teams.

Quick Start

Create a new Architecture Decision Record for 'API Gateway Selection'.

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

An architecture decision record (ADR) documents critical architectural choices, justifications, and consequences. You need to create one when making significant technical decisions, such as selecting a new database technology, to ensure choices are properly tracked and comply with organizational governance standards.

How do I document architecture decisions and identify the required approvers?

To document architecture decisions, you follow a guided process defining context, problem statements, alternatives, decisions, and consequences. The skill identifies required approvers based on subject matter expertise and organizational policies, ensuring compliance with architectural governance standards.

What should be included in an architecture decision record for a new technology selection?

An architecture decision record for a new technology selection should include context, a problem statement, evaluated alternatives, the final decision, consequences, and implementation details. It also lists required approvers based on subject areas, such as Security, Data, and Engineering teams.

Can I use a standard template to generate an ADR for API Gateway Selection?

Yes, you can generate an architecture decision record for API Gateway Selection using a defined organizational process and template. The skill guides you through documenting the context, alternatives, decision, and consequences while ensuring compliance with organizational standards.

How do I ensure my technical decisions comply with organizational governance standards?

To ensure technical decisions comply with organizational governance standards, document them using an architecture decision record. The skill enforces this by guiding you through a defined template and identifying the required subject matter approvers needed to validate the architectural choice.