architecture-decision-records

Document architecture decisions and rationales using standardized ADR templates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Hanseooo/hanseo-opencode-workflows --skill architecture-decision-records-hanseooo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/Hanseooo/hanseo-opencode-workflows/tree/main/skills/architecture-decision-records
Command: npx skills add https://github.com/Hanseooo/hanseo-opencode-workflows --skill architecture-decision-records-hanseooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture Decision Records (ADRs) capture the context, rationale, decisions, and consequences behind significant architectural choices, preserving knowledge and reducing rework when teams scale or change.

Core Features & Use Cases

  • Templates for standard ADRs (Standard ADR, Lightweight ADR, Y-Statement) to document decisions consistently.
  • An ADR index and lifecycle (Proposed, Accepted, Deprecated, Superseded) to enable governance, traceability, and onboarding.
  • Automation-ready patterns (adr-tools integration, ADR directory structure, and review workflows) to streamline creation, linking, and maintenance.
  • Cross-project collaboration by providing a centralized record of architecture decisions and trade-offs.

Quick Start

Create a new ADR using the template and add it to the ADR index.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema
How do I document architecture decisions to preserve rationale and context?

Architecture Decision Records document decisions and rationales to preserve history and context. Using standardized templates, teams capture proposals, trade-offs, and consequences from initial proposal through to supersession, reducing rework during scaling.

What templates can I use to standardize architecture decision records?

Architecture decision records can be standardized using Standard ADR, Lightweight ADR, and Y-Statement templates. These formats ensure consistent documentation of context, decisions, and consequences, while linking to a centralized ADR index for governance.

How do I track the lifecycle status of an architecture decision record?

Architecture decision record lifecycle status is tracked through Proposed, Accepted, Deprecated, and Superseded states. This enables traceability and governance, ensuring teams know exactly which architectural choices are currently active across projects.

Can I automate architecture decision record creation and maintenance workflows?

Architecture decision records support automation-ready patterns for creation, linking, and maintenance. The directory structure integrates with automation tools like adr-tools to streamline review workflows and keep the ADR index updated automatically.

When do I need to create lightweight architecture decision records?

Lightweight architecture decision records are needed when teams require rapid documentation of architectural choices without the overhead of full context. They fit smaller technical decisions while still maintaining traceability within the broader ADR index.

Does this approach to architecture decision records work for cross-project collaboration?

Architecture decision records facilitate cross-project collaboration by providing a centralized record of architectural decisions and trade-offs. This standardized documentation enables consistent onboarding and governance across multiple technical teams.