architecture-decision-records

Name: architecture-decision-records
Availability: InStock
Author: Fran

Capture architectural decisions with context, rationale, and consequences using a standard template.

Updated Aug 27, 2026

Search Tags:#architecture #documentation #adr #software-engineering #design-decisions #engineering-workflow

Ready to run

npx skills add https://github.com/franciscosanchezn/easyfactu-es --skill architecture-decision-records-franciscosanchezn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/franciscosanchezn/easyfactu-es/tree/main/.github/skills/architecture-decision-records
Command: npx skills add https://github.com/franciscosanchezn/easyfactu-es --skill architecture-decision-records-franciscosanchezn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture teams often struggle to preserve the rationale behind strategic decisions. This Skill standardizes the capture of architectural decisions, including context, trade-offs, and consequences, making them easy to revisit and reason about over time.

Core Features & Use Cases

ADR creation and formatting: Use the standard template to document decisions with a consistent structure.
Decision lifecycle awareness: Track Proposed, Accepted, Deprecated, and Superseded states to manage evolution.
Indexing and discovery: Maintain an ADR index to quickly locate decisions relevant to a project or domain.
Onboarding and knowledge transfer: Help new engineers understand past choices by reading well-structured ADRs.
Use case alignment: Document decisions when selecting frameworks, patterns, or tools to ensure traceability.

Quick Start

Create a new ADR by copying the template, filling the Context, Decision, and Consequences sections, then update 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 with context and rationale?▼

To document architectural decisions, use a standard ADR template to capture context, decision, and consequences. This standardizes design rationale, making trade-offs easy to revisit and reason about over time across projects.

What is an ADR lifecycle and how do I track decision status?▼

An ADR lifecycle tracks the evolution of architectural decisions through Proposed, Accepted, Deprecated, and Superseded states. This lifecycle awareness manages decision changes and maintains historical traceability for engineering teams.

How do I create an architecture decision record for choosing a new framework?▼

Create an architecture decision record by copying a standard template, filling the Context, Decision, and Consequences sections, then updating the ADR index to ensure the framework selection remains traceable and discoverable.

When do I need to write architecture decision records?▼

Write architecture decision records when choosing frameworks, patterns, or tech standards, onboarding engineers, or revisiting past decisions. ADRs preserve the strategic rationale behind engineering workflow choices and ensure traceability.

How do I maintain an ADR index for software engineering documentation?▼

Maintain an ADR index by updating it whenever a new architecture decision record is created or its lifecycle status changes. This indexing ensures quick discovery of decisions relevant to a specific project or domain.

Does this ADR format enforce frontmatter and consistent structure?▼

Yes, the ADR format enforces frontmatter presence and consistent structure across all architecture decision records. This standardization ensures decisions remain uniformly formatted, readable, and easy to parse over time.