How do I install the Adr skill?

Run npx skillmds@latest add majiayu000/adr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Adr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Adr by majiayu000 — Agent Skill

File contents

INSTRUCTIONS

Manage Architecture Decision Records (ADRs) throughout their lifecycle: read existing decisions, write new ones, and ensure development aligns with documented decisions.

Template: See template.md for the MADR structure (status, context, drivers, options, consequences)
Operations: See operations.md for directory discovery, naming conventions, commit integration, deprecation (_ prefix), and ADR-aligned development workflow
Queries: See queries.md for finding ADRs by topic, status, or relationship

Modes

Read Mode

Trigger: "why did we choose X?", "what's our approach to Y?", "is there an ADR for Z?"

Discover ADR directory (see operations.md)
Search for relevant ADRs by keyword/topic
Summarize the decision and its rationale
Note if the ADR is active, deprecated, or superseded

Write Mode

Trigger: "we should use", "let's go with", "I've decided to", trade-off discussions

Check for existing ADRs on the topic (may need to supersede)
Gather information through clarifying questions
Draft ADR using template.md
Save and commit (amend later if needed)

ADR-Aligned Development Mode

Trigger: Implementing features, making architectural changes, deviating from existing patterns

Before implementation: Check for relevant ADRs
During implementation: Reference ADR in commits
On completion: Update ADR status (proposed → accepted)
On deviation: Create superseding ADR, deprecate old one with _ prefix

Quality Checklist

Before finalizing an ADR:

Title clearly states the decision (not the problem)
Context explains WHY this decision is needed now
At least 2 options were genuinely considered
Decision drivers link to actual project constraints
Consequences include both positive AND negative impacts
Confirmation section describes how to validate the decision

Anti-Patterns

Decision without options: Always document alternatives considered
Vague consequences: Be specific about trade-offs
Missing "why": The ADR should answer "why this, why now"
Orphan ADRs: Link to related ADRs when relevant
Stale ADRs: Update status when implemented or superseded
Undocumented deviation: If you deviate from an ADR, create a new one

Reference

Based on MADR - Markdown Architectural Decision Records (Version 4.0, 2024)

---name: adrdescription: Manages Architecture Decision Records (ADRs) throughout their lifecycle, including reading, writing, and aligning development with documented decisions.---# INSTRUCTIONSManage Architecture Decision Records (ADRs) throughout their lifecycle: read existing decisions, write new ones, and ensure development aligns with documented decisions.- **Template**: See `template.md` for the MADR structure (status, context, drivers, options, consequences)- **Operations**: See `operations.md` for directory discovery, naming conventions, commit integration, deprecation (`_` prefix), and ADR-aligned development workflow- **Queries**: See `queries.md` for finding ADRs by topic, status, or relationship## Modes### Read Mode**Trigger**: "why did we choose X?", "what's our approach to Y?", "is there an ADR for Z?"1. Discover ADR directory (see `operations.md`)2. Search for relevant ADRs by keyword/topic3. Summarize the decision and its rationale4. Note if the ADR is active, deprecated, or superseded### Write Mode**Trigger**: "we should use", "let's go with", "I've decided to", trade-off discussions1. Check for existing ADRs on the topic (may need to supersede)2. Gather information through clarifying questions3. Draft ADR using `template.md`4. Save and commit (amend later if needed)### ADR-Aligned Development Mode**Trigger**: Implementing features, making architectural changes, deviating from existing patterns1. **Before implementation**: Check for relevant ADRs2. **During implementation**: Reference ADR in commits3. **On completion**: Update ADR status (proposed → accepted)4. **On deviation**: Create superseding ADR, deprecate old one with `_` prefix## Quality ChecklistBefore finalizing an ADR:- [ ] Title clearly states the decision (not the problem)- [ ] Context explains WHY this decision is needed now- [ ] At least 2 options were genuinely considered- [ ] Decision drivers link to actual project constraints- [ ] Consequences include both positive AND negative impacts- [ ] Confirmation section describes how to validate the decision## Anti-Patterns- **Decision without options**: Always document alternatives considered- **Vague consequences**: Be specific about trade-offs- **Missing "why"**: The ADR should answer "why this, why now"- **Orphan ADRs**: Link to related ADRs when relevant- **Stale ADRs**: Update status when implemented or superseded- **Undocumented deviation**: If you deviate from an ADR, create a new one## ReferenceBased on [MADR - Markdown Architectural Decision Records](https://adr.github.io/madr/) (Version 4.0, 2024)

Frequently asked questions

Adr