architecture-decision-review

Evaluate proposed architectural decisions and generate Architecture Decision Records.

12|1|Updated Jun 4, 2013
One-click install
npx skills add https://github.com/bostonaholic/dotfiles --skill architecture-decision-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-review
Source: https://github.com/bostonaholic/dotfiles/tree/main/claude/skills/architecture-decision-record
Command: npx skills add https://github.com/bostonaholic/dotfiles --skill architecture-decision-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions are often made informally, leading to inconsistent rationale and fragile long-term maintainability. This framework ensures deliberate evaluation and durable documentation of Architecture Decision Records (ADRs).

Core Features & Use Cases

  • Structured decision review: clarify problems, enumerate alternatives, and compare options using defined quality attributes.
  • ADR generation: produce Architecture Decision Records with a standard template to formalize outcomes.
  • Governance and traceability: document risks, decisions, and follow-ups to support future migrations or reversals.

Quick Start

Generate a concise ADR outline for your proposed architectural decision.

Frequently Asked Questions about architecture-decision-review

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

An Architecture Decision Record (ADR) documents the rationale behind a significant architectural choice. You need an ADR when evaluating new services, major infrastructure patterns, data model changes, technology adoptions, or reversing prior decisions to ensure durable traceability.

How do I evaluate architectural alternatives against quality attributes?

To evaluate architectural alternatives, clarify the problem context, enumerate available options, and assess each alternative against defined quality attributes. This structured decision review identifies risks and makes the final architecture decision explicit within the generated ADR.

How do I write an ADR for a new infrastructure pattern or technology adoption?

Writing an ADR involves applying a structured workflow: clarify the problem, enumerate alternatives, assess options against quality attributes, identify risks, make the decision explicit, and provide a migration plan using a standard ADR template to formalize the outcome.

Can I use this framework to reverse a prior architectural decision?

Yes, you can use this framework to reverse prior architectural decisions. It evaluates the reversal by clarifying the new context, assessing alternatives against quality attributes, identifying risks, and generating an ADR with a migration or follow-up plan for the transition.

What is the best way to document risks and follow-up plans for architectural decisions?

The best way to document risks and follow-up plans is by generating an Architecture Decision Record. The ADR template captures the evaluated alternatives, identifies specific risks, makes the decision explicit, and outlines the migration or follow-up plan for future governance.