Docs
635 installs
architecture-decision-records
by wshobson/agents
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant…
Skill content
Document significant technical decisions with structured context, rationale, and consequences. - Provides five template formats (standard MADR, lightweight, Y-statement, deprecation, RFC-style) covering different decision complexity levels and team preferences - Includes lifecycle management patterns for proposed, accepted, deprecated, and superseded decisions with clear status tracking - Offers directory structure, indexing strategies, and automation tools (adr-tools) for maintaining ADR repositories at scale - Covers review processes, best practices, and migration patterns for deprecating or superseding previous architectural choices Architecture Decision Records Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions. When to Use This Skill - Making significant architectural decisions - Documenting technology choices - Recording design trade-offs - Onboarding new team members - Reviewing historical decisions - Establishing decision-making processes Core Concepts 1. What is an ADR? An Architecture Decision Record captures: