skills.rest
Clean1ines
Clean1inesCOMMUNITY
Explore all skills by this author →
GitHub

architecture-decision-records

Capture architectural decisions as structured ADRs with context, alternatives, and rationale.

Updated Mar 16, 2026
Search Tags:#workflow#architecture#documentation#adr#software-design#decision-records
One-click install
npx skills add https://github.com/Clean1ines/crm_bot --skill architecture-decision-records-clean1ines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/Clean1ines/crm_bot/tree/main/.agents/skills/ecc/architecture-decision-records
Command: npx skills add https://github.com/Clean1ines/crm_bot --skill architecture-decision-records-clean1ines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions often live in Slack threads, PR comments, or memory, making it hard to find and justify later. This Skill provides a structured ADR workflow that records decisions as authoritative documents attached to the codebase.

Core Features & Use Cases

  • ADR capture: Detect decision moments and generate ADRs with context, alternatives considered, and rationale.
  • ADR catalog: Maintain a central log of ADRs alongside the project for traceability.
  • Workflow integration: Supports planning, design reviews, onboarding, and handoffs to explain design choices.

Quick Start

Record the current architectural decision as an ADR with context, alternatives, 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 capture architectural decisions as structured records alongside my code?▼

Architecture decision records are captured during coding sessions by detecting decision moments and generating ADRs that include context, alternatives considered, and rationale. These records are stored as authoritative documents directly attached to the codebase.

What is the best way to maintain an architecture decision log for traceability?▼

The best way to maintain an architecture decision log is using a central ADR catalog that indexes all records alongside the project, preserving traceability and ensuring design choices remain accessible for future reference.

How do I integrate architecture decision records into my software design workflow?▼

Architecture decision records integrate into software design workflows by supporting planning, design reviews, onboarding, and handoffs, capturing decisions with context and rationale as they happen rather than leaving them in scattered communication threads.

When do I need to document software design decisions using ADRs?▼

You need to document software design decisions using ADRs when architectural choices require long-term justification, ensuring that context, alternatives, and rationale are preserved as authoritative documents within the codebase.

Can I generate architecture decision records during planning and design reviews?▼

Yes, architecture decision records can be generated during planning and design reviews by recording decisions with context, alternatives, and rationale as they occur, ensuring the ADR workflow captures every significant design choice.

Related Skills

Explore More Software Engineering Skills→
arbisoftarbisoft
4

architecture-decision-records

Generate structured ADR documents with context, decision, alternatives, and consequences.

Official
Advanced
dapperdiversdapperdivers
1

vault-indexer

Index Obsidian vault metadata into a SQLite database for structured note retrieval.

Community
Advanced
HardyLiu6HardyLiu6

finishing-a-development-branch

Finalize a development branch with merge, pull request, or cleanup options.

Community
Advanced
jonnymuirjonnymuir
1

Design Docs ↔ Issues ↔ Decisions Bridge Pattern

Standardize design documentation, execution tasks, and architectural decisions across multi-specialist projects.

Community
Intermediate