How do I install the Adr skill?

Run npx skillmds@latest add diegosouzapw/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.

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. 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.

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

Adr by diegosouzapw — Agent Skill

Name: Adr
Rating: 4.2 (5 reviews)
Author: diegosouzapw

File contents

/adr

Create Architecture Decision Records through interactive conversation.

Usage

/adr                                      # Start conversation
/adr "database selection for coordinatr"  # Provide topic

Output Location

ADRs live with code in spaces/:

spaces/[project]/docs/project/adrs/
├── ADR-001-database-choice.md
├── ADR-002-auth-strategy.md
└── ADR-003-testing-strategy.md

Execution Flow

1. Gather Context

# Current architecture
Read: spaces/[project]/docs/project/architecture-overview.md

# Existing ADRs
Glob: spaces/[project]/docs/project/adrs/ADR-*.md

# Project context
Read: ideas/[project]/project-brief.md

# Relevant research
Glob: resources/research/*.md

2. Interactive Conversation

Ask one at a time:

What decision needs to be made?
Why is this decision needed now?
What options are you considering? (2-4 alternatives)
What are the constraints? (time, budget, skills)
What are the trade-offs for each?
Which option do you prefer and why?

3. Research Support

If user unsure about options:

Check existing research in resources/research/
Suggest /research for deeper dive
Use WebSearch for current best practices

4. Create ADR Document

# ADR-###: [Decision Title]

**Status**: Accepted
**Date**: YYYY-MM-DD
**Decision Makers**: [who was involved]

## Context
[Why this decision is needed]

## Decision
We will use **[chosen option]** because [rationale].

## Options Considered

### Option 1: [Name]
**Pros**: ...
**Cons**: ...

### Option 2: [Name]
**Pros**: ...
**Cons**: ...

## Consequences

### Positive
- What we gain

### Negative
- What we lose
- Technical debt accepted

### Risks
- Risk and mitigation

## Related Decisions
- Links to related ADRs/specs

## References
- Documentation links

When to Use

Technology/framework selection
Architecture patterns
Third-party service choices
Data modeling approaches
Cross-project standards

Not for: Implementation details, temporary decisions, already-decided standards

ADR Lifecycle

Accepted - Decision made, actively followed
Deprecated - No longer relevant
Superseded - Replaced by newer ADR

Workflow

/brief -> /research -> /adr -> /spec

---name: adrdescription: Create Architecture Decision Records through interactive conversation. Use when making technology choices, architecture patterns, or third-party service selections.---# /adrCreate Architecture Decision Records through interactive conversation.## Usage```bash/adr # Start conversation/adr "database selection for coordinatr" # Provide topic```## Output LocationADRs live with code in `spaces/`:```spaces/[project]/docs/project/adrs/├── ADR-001-database-choice.md├── ADR-002-auth-strategy.md└── ADR-003-testing-strategy.md```## Execution Flow### 1. Gather Context```bash# Current architectureRead: spaces/[project]/docs/project/architecture-overview.md# Existing ADRsGlob: spaces/[project]/docs/project/adrs/ADR-*.md# Project contextRead: ideas/[project]/project-brief.md# Relevant researchGlob: resources/research/*.md```### 2. Interactive ConversationAsk one at a time:1. **What decision needs to be made?**2. **Why is this decision needed now?**3. **What options are you considering?** (2-4 alternatives)4. **What are the constraints?** (time, budget, skills)5. **What are the trade-offs for each?**6. **Which option do you prefer and why?**### 3. Research SupportIf user unsure about options:- Check existing research in `resources/research/`- Suggest `/research` for deeper dive- Use WebSearch for current best practices### 4. Create ADR Document```markdown# ADR-###: [Decision Title]**Status**: Accepted**Date**: YYYY-MM-DD**Decision Makers**: [who was involved]## Context[Why this decision is needed]## DecisionWe will use **[chosen option]** because [rationale].## Options Considered### Option 1: [Name]**Pros**: ...**Cons**: ...### Option 2: [Name]**Pros**: ...**Cons**: ...## Consequences### Positive- What we gain### Negative- What we lose- Technical debt accepted### Risks- Risk and mitigation## Related Decisions- Links to related ADRs/specs## References- Documentation links```## When to Use- Technology/framework selection- Architecture patterns- Third-party service choices- Data modeling approaches- Cross-project standards**Not for**: Implementation details, temporary decisions, already-decided standards## ADR Lifecycle1. **Accepted** - Decision made, actively followed2. **Deprecated** - No longer relevant3. **Superseded** - Replaced by newer ADR## Workflow```/brief -> /research -> /adr -> /spec```

Frequently asked questions

Adr