adr-patterns

Name: adr-patterns
Availability: InStock
Author: cooldaemon

Create Architecture Decision Records using templates and naming conventions.

Updated Aug 23, 2026

Search Tags:#architecture #templates #decision making #documentation #adr #patterns

Ready to run

npx skills add https://github.com/cooldaemon/dotfiles --skill adr-patterns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adr-patterns
Source: https://github.com/cooldaemon/dotfiles/tree/main/.claude/skills/adr-patterns
Command: npx skills add https://github.com/cooldaemon/dotfiles --skill adr-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized and structured approach to documenting significant architectural decisions, ensuring clarity, consistency, and maintainability of architectural choices over time.

Core Features & Use Cases

ADR Templates: Offers a ready-to-use template for creating Architecture Decision Records.
Naming Conventions: Defines a clear format for naming ADR files for easy identification and sorting.
Lifecycle Management: Outlines how ADRs should be managed, updated, and superseded.
Use Case: When deciding on a new database technology for a project, use this Skill to create an ADR that captures the context, considered options, the final decision, and its consequences.

Quick Start

Create a new Architecture Decision Record using the provided template and naming convention.

Frequently Asked Questions about adr-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) documents significant technology and design choices within a software project. You need an ADR to capture the context, considered options, final decision, and consequences for future reference and auditing.

How do I document architectural decisions effectively?▼

Document architectural decisions effectively by using a standardized ADR template and naming convention. This structured framework captures rationale, ensures clarity, consistency, and maintainability of architectural choices over time.

How do I manage the lifecycle of an Architecture Decision Record?▼

Manage the lifecycle of an Architecture Decision Record by following standardized conventions for updating and superseding files. This framework outlines how to maintain records so architectural rationale remains accessible and accurate throughout the project.

Does this approach to documenting architecture require specific dependencies?▼

No, this approach to documenting architecture requires no specific dependencies. It provides a standalone framework and ready-to-use templates for recording technology and design choices directly within your software projects.

What is the best way to name Architecture Decision Record files?▼

The best way to name Architecture Decision Record files is using a clear, standardized format defined by the framework. Proper naming conventions ensure easy identification and sorting of decision records within your project repository.