
Architecture Decision Records
This automatically captures architectural decisions during Claude Code sessions and writes them as structured ADRs in a docs/adr directory. It watches for decision moments like "let's go with X instead of Y" and prompts you to record the context, alternatives considered, and trade-offs. The format is Michael Nygard's lightweight ADR template, adapted for AI pair programming. It maintains an index so you can look up why a choice was made months later. The real value is making implicit decisions explicit before they disappear into Slack history. It asks for confirmation before creating files, which is the right move since it's modifying your repo structure.
- skills.sh installs
- 5.9K
- GitHub stars
- 300.3K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add affaan-m/ecc --skill architecture-decision-records --agent claude-codeInstalls into .claude/skills of the current project.
Files
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:
# ADR-NNNN: [Decision Title]
**Date**: YYYY-MM-DD
**Status**: proposed | accepted | deprecated | superseded by ADR-NNNN
**Deciders**: [who was involved]
## Context
What is the issue that we're seeing that is motivating this decision or change?
[2-5 sentences describing the situation, constraints, and forces at play]
## Decision
What is the change that we're proposing and/or doing?
Sponsors
Details
- Repository
- github.com/affaan-m/ecc
- Categories
- Code Review & Quality, Productivity & Planning
- First seen
- Jul 14, 2026
More from affaan-m/ecc
All 263- Deployment Patterns5.8K
- React Testing5.8K
- Pytorch Patterns5.8K
- Hexagonal Architecture5.8K
- Flutter Dart Code Review5.8K
- Frontend A11y5.8K
- Error Handling5.8K
- Ui Demo5.8K
- Agentic Engineering5.8K
- Vite Patterns5.8K
- Bun Runtime5.8K
- Agent Architecture Audit5.8K
- Nodejs Keccak2565.8K
- Security Scan5.8K
- Cpp Testing5.8K
- Django Tdd5.8K
- Dashboard Builder5.7K
- Redis Patterns5.7K
- Eval Harness5.7K
- Manim Video5.7K
- Content Engine5.7K
- Springboot Tdd5.7K
- Motion Patterns5.7K
- Configure Ecc5.7K