architecture-decision-records

Capture and organize architectural decisions as ADR documents with context and rationale.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/richardnpaul/everything-vscode-copilot --skill architecture-decision-records-richardnpaul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/richardnpaul/everything-vscode-copilot/tree/main/.github/skills/architecture-decision-records
Command: npx skills add https://github.com/richardnpaul/everything-vscode-copilot --skill architecture-decision-records-richardnpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures and standardizes architectural decisions as formal ADRs, ensuring rationale, context, and alternatives are documented alongside the codebase.

Core Features & Use Cases

  • Record decision moments during coding sessions with automated or guided ADR creation.
  • Maintain an ADR log with context, alternatives considered, and rationales to aid future developers.
  • Read existing ADRs and query reasons behind design choices for onboarding and reviews.

Quick Start

Record a new ADR detailing the current architectural decision including context, alternatives 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 and rationale during a coding session?

You can document architectural decisions during coding sessions by using automated ADR creation to capture context, alternatives considered, and rationale. This builds a durable ADR log that helps future developers understand why the codebase is shaped a certain way.

What is the best way to maintain an architecture decision log for a software project?

The best way to maintain an architecture decision log is to enforce a lightweight ADR format that tracks decision status and maintains an index. This organizes architectural decisions into a durable record for onboarding and design reviews.

How do I track the status of architectural decisions in an ADR?

You can track the status of architectural decisions by enforcing a lightweight ADR format that records decision moments and maintains an ADR index. This ensures the rationale and context behind each design choice remain accessible to future developers.

Can I query existing ADRs to understand the reasons behind past design choices?

Yes, you can read existing ADRs and query the reasons behind design choices for onboarding and reviews. The ADR log maintains the context, alternatives considered, and rationales required to understand past architectural decisions.

Do I need a specific framework to capture architectural decisions as ADR documents?

No specific framework is required to capture architectural decisions. The process automates ADR document creation during design reviews or coding sessions, enforcing a lightweight format without external dependencies to record decision moments and context.

When should I record an architectural decision in an ADR?

You should record an architectural decision whenever a design choice is made during coding sessions or design reviews. Capturing the decision moment, context, alternatives, and rationale ensures the reasoning is standardized and documented alongside the codebase.