architecture-decision-records

Record architectural decisions as ADR documents with rationale and trade-offs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/lllooollpp/solopreneur- --skill architecture-decision-records-lllooollpp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/lllooollpp/solopreneur-/tree/main/solopreneur/data/skills/architecture-decision-records
Command: npx skills add https://github.com/lllooollpp/solopreneur- --skill architecture-decision-records-lllooollpp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture architectural decisions as ADRs to preserve rationale and context for future maintainers.

Core Features & Use Cases

  • Structured ADRs: Create lightweight Architecture Decision Records in ADR format to document decisions, context, alternatives, and consequences.
  • In-code and project-wide visibility: ADRs live alongside code, ensuring traceability with the repository.
  • Lifecycle-aware: Supports proposed, accepted, deprecated, and superseded ADRs, with an index and template workflow.

Quick Start

Initialize ADR logging when a decision moment arises and write a new ADR entry following the ADR workflow.

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 should I document one?

An Architecture Decision Record (ADR) captures the rationale, context, alternatives, and consequences of a architectural decision. You should document ADRs during coding sessions, design reviews, and planning phases to preserve context for future maintainers.

How do I create ADRs in my project repository?

To create ADRs, initialize ADR logging to generate a docs/adr directory with an index and template. Write a new ADR entry following the Michael Nygard format to log the decision, alternatives considered, and consequences.

How does the ADR lifecycle work when architectural decisions change?

The ADR lifecycle supports proposed, accepted, deprecated, and superseded states. When a decision changes, you mark the existing ADR as superseded and create a new proposed ADR, maintaining traceability through the directory index.

What is the best way to maintain architecture traceability alongside code?

The best way to maintain architecture traceability is to store ADRs in a docs/adr directory within your repository. This in-code visibility ensures design decisions and their trade-offs are versioned directly with the codebase.

Do I need a specific framework to start writing ADRs?

No specific framework is needed. The process enforces the lightweight Michael Nygard ADR format, requiring only a standard project repository to initialize the docs/adr directory, template workflow, and index.