adr-generator
SkillDev toolsYour AI can write Architectural Decision Records, the documents teams use to capture what was decided and why. This adds a specialist that turns a design choice into a clear, structured record that reads well for both people and other AI tools.
Available today. Use it from your connected AI after setup.
No other account needed.
Add it, then ask your AI to draft a record for a design choice you have made or are about to make. The more context you share about the decision, the more complete the record will be.
Then ask your AI: use the adr-generator skill
What your AI can do with it
- Write an architecture decision record for a design choice
- Capture what was decided and why in a structured format
- Format records so both people and AI can read them easily
- Produce thorough records that cover the decision in full
What this skill tells your AI
The instructions your AI receives, as published by codebygarv/ai-skills in skills/documentation/adr-generator/SKILL.md and read by ahel’s review.
Purpose
Document significant architectural choices in a lightweight, immutable Architecture Decision Record (ADR) following the Michael Nygard format to maintain long-term technical context.
When to Use
- Committing to a new framework, language, database, or major pattern.
- Changing an existing architectural standard or deprecating a system.
- Preserving the "why" behind non-obvious engineering decisions for future hires.
What to Analyze
- Title & Status:
[Number] [Title](e.g.ADR-0012 Use ClickHouse for Event Analytics) with status (Proposed,Accepted,Superseded,Rejected). - Context: What problem are we solving, and what business/technical constraints force a decision?
- Decision: The clear, active-voice statement of what is being adopted.
- Alternatives Considered: What other options were evaluated and why were they declined?
- Consequences: Positive effects, negative tradeoffs, and operational risks accepted.
Output Format
- Standard Markdown ADR template with YAML frontmatter.
- Clear, objective, concise sections without fluff.
Avoid
- Writing ADRs as post-hoc justifications with no alternatives mentioned.
- Omitting negative consequences and maintenance burdens.
Signals
- GitHub stars
- 25
- Forks
- 1
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
adr-generator- Source
- github.com/codebygarv/ai-skills