create-adr
Creates Architecture Decision Records (ADRs) to document significant architectural choices and their rationale for future team members. Use when the user says "write an ADR", "document this decision", "record why we chose X", "add an architecture decision record", "create an ADR for", or wants to capture the reasoning behind a technical choice so the team understands it later. Do NOT use when the decision hasn't been made yet (use create-rfc instead), for implementation planning (use technical-design-doc-creator), or for general documentation.
npx skills add tech-leads-club/agent-skills --skill create-adr --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ADR Creator You are an expert in creating Architecture Decision Records (ADRs) — concise, durable documents that capture the context, decision, and consequences of significant architectural choices so future team members understand *why* things are the way they are. ## When to Use This Skill Use this skill when: - User asks to "write an ADR", "create an ADR", "add an architecture decision record" - User wants to "document why we chose X", "record this decision", "capture this architectural choice" - A significant technical decision has been made (or is being finalized) and needs to be recorded - The team wants to preserve the reasoning behind a choice for future engineers - User asks "why did we choose X" and the answer should be written down permanently Do NOT use for: - Decisions not yet made — use `create-rfc` to drive the decision process first - Implementation planning after the decision — use `technical-design-doc-creator` - Simple configuration choices or trivial code decisions - Meeting notes or general documentation ## ADR vs RFC — Critical Distinction | Aspect | ADR | RFC | |--------|-----|-----| | **Timing** | Decision already made (or being finalized) | Before the dec
- When to Use This Skill
- ADR vs RFC — Critical Distinction
- Language Adaptation
- ADR Format Selection
- Interactive Workflow
- Step 1: Gather Context (if not provided)
- Step 2: Validate Mandatory Fields
- Step 3: Assign ADR Number
- Step 4: Generate the ADR
- Step 5: Offer File Placement
- Document Templates
- MADR Format (Default)
- Nygard Format (Minimal)
- Y-Statement Format (Compact)
What does the create-adr skill do?
Creates Architecture Decision Records (ADRs) to document significant architectural choices and their rationale for future team members. Use when the user says "write an ADR", "document this decision", "record why we chose X", "add an architecture decision record", "create an ADR for", or wants to capture the reasoning behind a technical choice so the team understands it later. Do NOT use when the decision hasn't been made yet (use create-rfc instead), for implementation planning (use technical-design-doc-creator), or for general documentation.
How do I install it?
Run `npx skills add tech-leads-club/agent-skills --skill create-adr --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tech-leads-club/agent-skills, a repository with 4,983 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.