ReddRadar
Agent skill
adr
Create Architecture Decision Records through interactive conversation. Use when making technology choices, architecture patterns, or third-party service selections.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/adr-taylorhuston-local-life-manager
SKILL.md
/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
/researchfor 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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?