architecture-decision-recorder
Create and manage Architecture Decision Records (ADRs) for documenting important architectural decisions, tradeoffs, and rationale.
Best use case
architecture-decision-recorder is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create and manage Architecture Decision Records (ADRs) for documenting important architectural decisions, tradeoffs, and rationale.
Teams using architecture-decision-recorder should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/architecture-decision-recorder/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How architecture-decision-recorder Compares
| Feature / Agent | architecture-decision-recorder | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create and manage Architecture Decision Records (ADRs) for documenting important architectural decisions, tradeoffs, and rationale.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 ```markdown # 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
Related Skills
architecture-specialist
提供系统架构设计、技术选型、架构审查和组件设计能力。当需要设计新系统、重构现有架构或进行架构审查时使用。
architecture-decision-records
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
architecture-decision-record
ADR format and methodology for documenting significant technical decisions with context, alternatives considered, and consequences. Use when making or documenting architectural decisions.
alibaba-cloud-architecture
Alibaba Cloud architecture patterns and best practices. Use when designing, deploying, or reviewing infrastructure on Alibaba Cloud including ECS, ACK, Function Compute, and OSS.
5w1h-decision
5W1H Decision Framework Tool. Use for: (1) Systematic decision-making before creating todos, (2) Preventing duplicate implementation, (3) Detecting avoidance behavior, (4) Ensuring agile refactor compliance with executor/dispatcher separation
Tech Stack & Architecture Decision
Define and document the technology stack and architecture decisions for a project. Use when the user needs to choose a tech stack, make architecture decisions, define infrastructure choices, or document technology selections. Triggers on requests like "define the tech stack", "choose technologies", "architecture decisions", "what stack should we use", or any request to select and document frontend, backend, database, auth, hosting, and infrastructure choices for a project.
springboot-architecture-analyzer
系統化分析 Spring Boot 專案並生成完整的企業級架構文件,涵蓋系統概述、架構視圖、技術細節、部署策略等所有關鍵面向。
software-architecture
Design scalable software systems with proven architectural patterns (MVC, microservices, event-driven), SOLID principles, system design trade-offs, and architectural decision records (ADRs).
reviewing-python-architecture
Review ADRs to check they follow testing principles and parent PDR constraints. Use when reviewing ADRs or architecture decisions.
review-architecture
Verify DDD patterns, Clean Architecture boundaries, and bITdevKit-specific conventions in modular monolith projects
react-native-architecture
Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecti...
react-gradual-architecture
Incremental React code organization guidelines. Start small, then extract when scanning and responsibilities start to blur. Use when creating features, organizing files, refactoring components, or deciding when to extract hooks, UI, or utils.