Individual skill
adr-generator
Formats Architecture Decision Records (ADRs) capturing problem context, considered alternatives, and consequences.
skills/documentation/adr-generator/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 553 bytesSKILL.mdcore · 1,408 bytesexamples/example.mddoc · 995 bytes
Read excerpt
## 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
1. **Title & Status**: `[Number] [Title]` (e.g. `ADR-0012 Use ClickHouse for Event Analytics`) with status (`Proposed`, `Accepted`, `Superseded`, `Rejected`).
2. **Context**: What problem are we solving, and what business/technical constraints force a decision?