architecture-decision-records
This skill captures architectural decisions made during coding sessions as structured ADR documents that live alongside your codebase. It detects decision moments, gathers context and alternatives, and maintains a searchable log so future developers understand the reasoning behind your architecture.
Architecture Decision Records captures and documents your architectural choices as structured ADRs during development.
AI-generated summary based on this skill's SKILL.md
Install
affaan-m/ECC/architecture-decision-records · repository language: JavaScript
git clone https://github.com/affaan-m/ECC
cp -r ECC/skills/architecture-decision-records ~/.claude/skills/architecture-decision-recordsnpx skillfed install affaan-m/ECC/architecture-decision-recordsFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does architecture-decision-records help document architectural decisions?
architecture-decision-records captures architectural decisions made during development as structured ADR documents that live alongside your codebase. It detects decision moments, gathers context and alternatives, and maintains a searchable log so future developers understand the reasoning behind your architecture.
What should an ADR template for code projects include?
architecture-decision-records generates ADR templates that structure decisions with context, alternatives considered, and the rationale for your choice. Each record captures why a particular architectural path was selected, what other options were evaluated, and the trade-offs involved in the decision.
Can architecture-decision-records record alternatives considered in design?
Yes. architecture-decision-records is designed to document not just the decision made, but also the alternatives that were considered and rejected. This captures the full decision-making context, helping teams understand why certain frameworks, patterns, or technologies were chosen over others.
How do I maintain an architecture decision history with this skill?
architecture-decision-records maintains a searchable log of all technology and design decisions over time. By recording each architectural choice as a structured document in your codebase, you build a persistent history that tracks consequences and trade-offs, making it easy to reference past reasoning when similar decisions arise.
Why did we choose this framework—how can ADRs help answer that?
architecture-decision-records lets you document framework selection rationale directly in your codebase. When team members ask why a particular framework was chosen, they can search the ADR log to find the original decision record explaining the evaluation criteria, alternatives considered, and the reasoning behind the selection.
Can architecture-decision-records auto-generate decision records?
architecture-decision-records streamlines ADR creation by helping you capture decision context and structure it into formal records. While it guides the documentation process, the skill focuses on making it easy to record and maintain decision logs so your team builds a comprehensive architecture decision tracking system over time.
SKILL.md
rendered from the published skill — quoted content, verbatim
Architecture Decision Records
Capture architectural decisions as they happen during coding sessions. Instead of decisions living only in Slack threads, PR comments, or someone's memory, this skill produces structured ADR documents that live alongside the code.
When to Activate
- User explicitly says "let's record this decision" or "ADR this"
- User chooses between significant alternatives (framework, library, pattern, database, API design)
- User says "we decided to..." or "the reason we're doing X instead of Y is..."
- User asks "why did we choose X?" (read existing ADRs)
- During planning phases when architectural trade-offs are discussed
ADR Format
Use the lightweight ADR format proposed by Michael Nygard, adapted for AI-assisted development:
```markdown
ADR-NNNN: [Decision Title]
Date: YYYY-MM-DD Status:
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
skills/architecture-decision-records/SKILL.md