creating-adr

Create Architecture Decision Records with standardized templates in docs/adr directories.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/k2works/claude-code-booster --skill creating-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-adr
Source: https://github.com/k2works/claude-code-booster/tree/main/lib/assets/.claude/skills/creating-adr
Command: npx skills add https://github.com/k2works/claude-code-booster --skill creating-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADR creation and management support for Architecture Decision Records (ADRs) with a standardized template and best practices to document architectural decisions.

Core Features & Use Cases

  • Provides ADR templates and guidance on file structure to ensure consistency across projects.
  • Facilitates tracking and collaboration by organizing decisions, contexts, alternatives, and confirmations.
  • Useful for teams that need auditable decision history during software architecture evolution.

Quick Start

Create the first ADR using the docs/adr structure to begin recording an architecture decision.

Frequently Asked Questions about creating-adr

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

FAQPage Schema
How do I document architecture decisions using an ADR template?

Architecture Decision Records provide a standardized, versioned format for documenting software architecture choices. They capture context, evaluated alternatives, and confirmations, creating an auditable history for teams during architecture evolution across backend and infrastructure domains.

How do I create an Architecture Decision Record directory structure?

Set up a docs/adr directory structure to organize ADR files, ensuring consistency across projects. This structure facilitates tracking and collaboration by systematically organizing contexts, alternatives, and confirmations for auditable decision history.

When do I need Architecture Decision Records for software architecture projects?

Use Architecture Decision Records when software architecture decisions require versioned, auditable documentation. They are applicable across backend, frontend, and infrastructure domains where tracking context, alternatives, and compliance checks is necessary for team collaboration.

What is the best way to track software architecture alternatives and compliance checks?

Track alternatives and compliance checks using standardized ADR templates within a docs/adr directory. This enforces best practices by systematically documenting context, alternatives, and confirmations, ensuring decisions remain auditable during software architecture evolution.

Can I use ADR templates for both frontend and backend infrastructure decisions?

Yes, ADR templates support documenting decisions across backend, frontend, and infrastructure domains. The standardized template enforces consistent documentation of context, alternatives, and compliance checks, making it applicable for all software architecture projects.