skills.rest
tranhieutt
tranhieuttCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-decision-records

Document technical decisions with context, alternatives, and consequences in Architecture Decision Records.

70|42|Updated Mar 27, 2026
Search Tags:#documentation#adr#governance#trade-offs#architectural-decisions#technical-communication
One-click install
npx skills add https://github.com/tranhieutt/software_development_department --skill architecture-decision-records-tranhieutt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/architecture-decision-records
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill architecture-decision-records-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams keep the reasoning behind major architectural decisions visible and understandable, preventing historical context from being lost when future contributors revisit the codebase.

Core Features & Use Cases

  • Structured ADR guidance: captures context, decision drivers, considered options, rationale, consequences, and status to standardize documentation.
  • Lifecycle tracking: outlines how records move through proposed, accepted, rejected, deprecated, and superseded states to clarify what is current.
  • Use Case: When selecting a database, framework, or API gateway, follow this Skill to compare alternatives, weigh trade-offs, and publish the resulting ADR for architecture reviews.

Quick Start

Draft an ADR summarizing the context, options, decision, and consequences for your current architecture change.

Frequently Asked Questions about architecture-decision-records

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) captures context, alternatives, and consequences for significant technical choices. You need an ADR when selecting frameworks, databases, APIs, or security patterns to prevent historical context from being lost.

How do I document architectural trade-offs for a new database or framework selection?▼

Document architectural trade-offs by capturing context, decision drivers, considered options, and rationale in an ADR. Weigh alternatives and publish the resulting record for architecture reviews to standardize technical communication.

How does ADR lifecycle tracking work for deprecated or superseded decisions?▼

ADR lifecycle tracking records move through proposed, accepted, rejected, deprecated, and superseded states. This lifecycle clarifies what architectural decisions are currently active and links related records for historical reference.

Can I use architecture decision records for complex software projects with multiple API integrations?▼

Architecture decision records are designed for complex software projects choosing new frameworks, databases, APIs, or security patterns. They ensure detailed rationale and lifecycle tracking for review and historical reference across teams.

What should I include in an ADR to standardize technical communication and governance?▼

Include context, decision drivers, considered options, rationale, consequences, and status in an ADR to standardize technical communication. This structured documentation supports governance and links related architectural decisions.

When should I not use an Architecture Decision Record?▼

Architecture Decision Records should not be used for minor implementation details. Reserve ADRs for significant architectural decisions where capturing trade-offs, alternatives, and consequences provides necessary governance and historical context.

Related Skills

Explore More Software Engineering Skills→
em-jonesem-jones
1

write-adr

Generate Architecture Decision Records documenting context, options, and outcomes.

Community
Basic
avgarciaavgarcia

adr-review

Review architecture decision records for missing decisions, risks, and structural gaps.

Community
Advanced
ascerra-fullsend-rehearsalascerra-fullsend-rehearsal

writing-adrs

Create and manage Architecture Decision Records for software architecture.

Official
Intermediate
KemingHeKemingHe
9

meeting-memo-creation

Generate markdown meeting memos with decisions, actions, owners, and deadlines.

Community
Intermediate