architecture-decision-records

Document and manage Architecture Decision Records with Markdown templates and frontmatter metadata.

6|Updated Mar 1, 2026

Search Tags:#architecture #templates #documentation #adr #lifecycle #decision-records

Ready to run

npx skills add https://github.com/ChrstprJohn/SamsonDentalCenter --skill architecture-decision-records-chrstprjohn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/ChrstprJohn/SamsonDentalCenter/tree/main/.agent/skills/SystemArchitecture/architecture-decision-records
Command: npx skills add https://github.com/ChrstprJohn/SamsonDentalCenter --skill architecture-decision-records-chrstprjohn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions require a disciplined, reusable record that captures context, alternatives, decisions, and consequences to inform current and future work.

Core Features & Use Cases

Provides standard ADR templates and structure for Context, Decision, and Consequences sections.
Supports linking related ADRs, lifecycle states, and references for governance and traceability.
Enables indexing, searching, and maintaining a decision history across projects and teams.

Quick Start

Copy the standard ADR template to docs/adr and fill in the required sections to begin recording decisions.

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 with ADRs?▼

Document architectural decisions using a standard Markdown structure with frontmatter metadata for name, status, and date. Fill in Context, Decision, and Consequences sections to capture critical project rationale and alternatives for future reference.

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

An Architecture Decision Record (ADR) is a structured Markdown document capturing context, alternatives, and consequences. You need one when making critical architectural choices to maintain a traceable decision history across engineering teams and projects.

How do I manage ADR lifecycle states and link related decisions?▼

Manage ADR lifecycle states using frontmatter metadata fields and link related decisions through reference sections. This enforces governance, provides traceability, and connects historical choices across multiple projects and time periods.

Can I use ADR templates for project governance and team decision tracking?▼

Yes, ADR templates support project governance and team decision tracking. They enforce standard Markdown structures to index, search, and maintain a consistent decision history across engineering teams and projects.

What's the best way to structure context, options, and rationale in decision records?▼

Structure decision records using standard templates with Context, Decision, and Consequences sections. This format captures options and rationale, enforcing a disciplined, reusable record that informs current and future engineering work.

How do I index and search historical architecture decisions across projects?▼

Index and search historical architecture decisions by storing standard Markdown ADRs with frontmatter metadata. This enables maintaining, searching, and reviewing a comprehensive decision history across engineering teams and time.