architecture-decision-records

Create and maintain Architecture Decision Records with standardized templates and an index.

Updated Feb 24, 2026

Search Tags:#architecture #templates #documentation #adr #governance #lifecycle

Ready to run

npx skills add https://github.com/chicanoandres702/SentientAIBrowser --skill architecture-decision-records-chicanoandres702

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/chicanoandres702/SentientAIBrowser/tree/main/.agents/workflows/architecture-decision-records
Command: npx skills add https://github.com/chicanoandres702/SentientAIBrowser --skill architecture-decision-records-chicanoandres702

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decision documentation enables teams to capture the context, rationale, and consequences of significant design choices in a consistent, auditable way.

Core Features & Use Cases

Standard ADR templates and lifecycle coverage to structure decisions.
Guidance for creating, reviewing, and updating records to improve governance and onboarding.
Support for linking related decisions and maintaining a searchable archive of past architecture choices.

Quick Start

Create a new ADR using the MADR/ADR templates 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 architectural decisions in a standardized way?▼

To document architectural decisions in a standardized way, you can use formal Architecture Decision Record (ADR) templates that capture context, decisions, and consequences. These templates enforce a defined structure with frontmatter, lifecycle stages, references, and an index.

What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) is a formal document used to capture the context, rationale, and consequences of significant design choices. You need an ADR during architecture initiatives, team onboarding, governance reviews, and retrospectives to maintain an auditable history.

How do I create and maintain an ADR index for past architecture choices?▼

To create and maintain an ADR index, generate new records using MADR or ADR templates and add them to a searchable archive. This index links related decisions and supports ongoing governance by tracking the lifecycle of past architecture choices.

Does this ADR template support governance and team onboarding workflows?▼

Yes, this ADR template supports governance and team onboarding workflows by providing guidance for creating, reviewing, and updating records. It helps new members understand past architecture choices through a formal, auditable structure.

What is the best way to capture the context and consequences of design choices?▼

The best way to capture the context and consequences of design choices is by using a formal ADR structure with defined frontmatter. This approach ensures that the rationale and impact of architecture decisions are documented consistently for retrospective reviews.

Are there limitations to using standardized templates for architecture governance?▼

Standardized ADR templates enforce a strict structure with frontmatter, lifecycle, and references for architecture governance. While this ensures auditability, teams must consistently update the index and link related decisions to avoid an incomplete archive of past choices.