Agent-Skills.md

Agent Skills: Architecture Decision Recorder

Create and manage Architecture Decision Records (ADRs) for documenting important architectural decisions, tradeoffs, and rationale.

UncategorizedID: dexploarer/hyper-forge/architecture-decision-recorder

Repository

dexploarer/hyper-forge
Prompt-or-Die-Labs
72

Install this agent skill to your local

pnpm dlx add-skill https://github.com/Prompt-or-Die-Labs/hyper-forge/tree/HEAD/.claude/skills/architecture-decision-recorder

Skill Files

Browse the full folder contents for architecture-decision-recorder.

Download Skill

Loading file tree…

.claude/skills/architecture-decision-recorder/SKILL.md

Skill Metadata

Name
architecture-decision-recorder
Description
Create and manage Architecture Decision Records (ADRs) for documenting important architectural decisions, tradeoffs, and rationale.

Architecture Decision Recorder

Systematically document architectural decisions using the ADR pattern.

When to Use

  • Documenting significant architectural decisions
  • Recording technology choices
  • Tracking design tradeoffs
  • Maintaining architectural history
  • Facilitating team communication

ADR Template

# ADR-NNNN: [Title]

**Date:** YYYY-MM-DD
**Status:** [Proposed | Accepted | Deprecated | Superseded]
**Decision Makers:** [Names]

## Context

What is the issue we're trying to solve? What are the forces at play?

### Business Context
- Business goal or requirement
- Constraints (time, budget, team)
- Stakeholder concerns

### Technical Context  
- Current system state
- Technical constraints
- Integration requirements

## Decision

We will [decision statement].

### Rationale
Why this approach over alternatives?

## Consequences

### Positive
- Benefit 1
- Benefit 2

### Negative  
- Tradeoff 1
- Tradeoff 2

### Risks
- Risk 1 → Mitigation strategy
- Risk 2 → Mitigation strategy

## Alternatives Considered

### Option 1: [Name]
**Pros:** [List]
**Cons:** [List]  
**Rejected because:** [Reason]

### Option 2: [Name]
**Pros:** [List]
**Cons:** [List]
**Rejected because:** [Reason]

## Implementation

- [ ] Action item 1
- [ ] Action item 2

## References

- [Link to research]
- [Related ADR]

Best Practices

  • ✅ Create ADRs for all major decisions
  • ✅ Keep ADRs immutable (supersede, don't edit)
  • ✅ Store in version control
  • ✅ Link related ADRs
  • ✅ Review quarterly
  • ✅ Include quantitative data

Related Commands

  • /adr-create - Create new ADR