architecture-decision-records

Document architectural decisions as ADRs with context, alternatives, and rationale.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/RogerioSobrinho/codeme-copilot --skill architecture-decision-records-rogeriosobrinho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/RogerioSobrinho/codeme-copilot/tree/main/skills/architecture-decision-records
Command: npx skills add https://github.com/RogerioSobrinho/codeme-copilot --skill architecture-decision-records-rogeriosobrinho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture architectural decisions as ADRs to provide a structured, auditable trail of why major design choices were made, preventing memory decay and reliance on institutional knowledge.

Core Features & Use Cases

  • Create ADR documents that capture context, alternatives considered, decisions, and rationale.
  • Maintain an ADR log with status, dates, and deciders to help future developers understand the codebase evolution.
  • Link ADRs to code changes and projects to support traceability across teams.

Quick Start

Record an architectural decision by creating a new ADR entry with context, options considered, and rationale.

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 to prevent loss of institutional knowledge?

Document architectural decisions by creating Architecture Decision Records that capture context, alternatives considered, and rationale, providing a structured, auditable trail of why major design choices were made.

What is the best way to maintain an ADR log for framework choices and infrastructure decisions?

Maintain an ADR log using a structured format that records status, dates, deciders, and consequences, helping future developers understand codebase evolution across framework choices, infrastructure, and data modeling.

How do I record context and alternatives considered for design trade-offs across teams?

Record design trade-offs by creating a new ADR entry that explicitly documents the context, options considered, decision, and rationale, ensuring traceability across teams and projects.

Can I link architecture decision records to code changes and projects for traceability?

Yes, ADRs can be linked to code changes and projects to support traceability across teams, capturing the codebase context and design decisions in an auditable format.

Does documenting rationale for design decisions require a specific workflow?

Documenting rationale requires a structured ADR workflow to record the date, status, deciders, and consequences, preventing memory decay and reliance on institutional knowledge.

When do I need to create architecture decision records for data modeling?

Create architecture decision records for data modeling when you need to capture major design choices, alternatives considered, and rationale to provide an auditable trail of codebase evolution.