architecture-decision-records

Standardize Architecture Decision Records with frontmatter metadata and lifecycle tracking.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Shaarav4795/ScholarFlow --skill architecture-decision-records-shaarav4795
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/Shaarav4795/ScholarFlow/tree/main/.agents/skills/architecture-decision-records
Command: npx skills add https://github.com/Shaarav4795/ScholarFlow --skill architecture-decision-records-shaarav4795

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture Decision Records provide a structured, auditable way to capture the context, rationale, and consequences of significant technical decisions, ensuring consistency and traceability across teams and projects.

Core Features & Use Cases

  • Create standardized Architecture Decision Records (ADRs) to document critical decisions and maintain a historical record.
  • Manage ADR lifecycles, link related ADRs, and reference governance or policy documents.
  • Onboard new engineers with a transparent rationale and decision history to accelerate alignment.

Quick Start

Create a new ADR using the Standard template to document a major architectural decision.

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) is a structured document capturing the context, rationale, and consequences of significant technical decisions. You need ADRs to ensure consistency and traceability across teams when making major architectural choices.

How do I standardize Architecture Decision Records across multiple projects?

To standardize Architecture Decision Records, apply prescribed templates, enforce frontmatter metadata, track document lifecycles, and cross-reference related ADRs to maintain a consistent, auditable historical record across projects.

How do I document the lifecycle and relationships of an Architecture Decision Record?

Document ADR lifecycles and relationships by tracking their status over time, linking related ADRs together, and referencing relevant governance or policy documents within the standardized frontmatter metadata.

Can I use Architecture Decision Records to onboard new engineers to a project?

Yes, Architecture Decision Records accelerate onboarding new engineers by providing a transparent rationale and decision history. This establishes clear alignment on why specific architectural choices were made across the team.

Does this Architecture Decision Record template enforce metadata governance?

Yes, the template enforces frontmatter metadata to define decision governance across projects. This ensures every Architecture Decision Record maintains structural consistency for auditing and reviewing historical decisions.