architecture-decision

Document architecture decisions using ADRs with context, options, and consequences.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/sahin/claude-skills --skill architecture-decision-sahin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/sahin/claude-skills/tree/main/architecture-decision
Command: npx skills add https://github.com/sahin/claude-skills --skill architecture-decision-sahin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions often get lost as teams shift, leading to repeated debates and inconsistent systems. This skill provides a structured approach to recording the context, trade-offs, and rationale behind major architectural choices so future engineers can understand the decision.

Core Features & Use Cases

  • Create ADRs following a standardized template to capture context, options, decision, and consequences.
  • Load and consult existing ADRs, tech stacks, roadmaps, and budget data to inform decisions.
  • Review ADRs over time to track outcomes and ensure traceability.

Quick Start

Create an ADR for a significant architecture decision in your project using the ADR template.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema
How do I document architecture decisions to prevent repeated debates?

Document architecture decisions using Architecture Decision Records (ADRs) to capture context, options, and consequences, ensuring future engineers can trace the rationale behind significant technical choices.

What is an ADR and when should I use it for engineering governance?

An ADR is a standardized record for capturing the context, trade-offs, and consequences of a technical decision, used when making significant, hard-to-reverse choices across systems, teams, and budgets.

How do I create an ADR that includes tech stack and roadmap context?

Create an ADR by loading existing records, current tech stacks, roadmaps, and budget data, then structuring the decision using an ADR template to ensure all relevant project context informs the outcome.

Can I use ADRs to track budget impact for hard-to-reverse technical decisions?

Yes, the ADR workflow loads budget data alongside roadmaps and tech stacks to inform significant technical decisions, ensuring that financial constraints and cross-team impacts are factored into the recorded rationale.

Where should I store architecture decision records for traceability?

Store architecture decision records under the data/engineering/adrs/ directory to maintain a structured repository, allowing teams to load, review, and track outcomes over time for consistent engineering governance.