AR

architecture-decision-records

It standardizes architectural documentation using the MADR format to track context, trade-offs, and decision statuses.

Install

mkdir -p .claude/skills/architecture-decision-records && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/453" && unzip -o skill.zip -d .claude/skills/architecture-decision-records && rm skill.zip

Installs to .claude/skills/architecture-decision-records

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

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.
246 chars✓ has a “when” trigger
Beginner

Key capabilities

  • →Document significant technical decisions
  • →Record architectural trade-offs and rationale
  • →Manage the lifecycle of architectural decisions
  • →Generate ADR indexes and tables of contents
  • →Link related architectural decisions

How it works

The skill utilizes the MADR format to capture the context, decision, and consequences of technical choices. It provides a structured lifecycle for decisions, moving from proposed to accepted, deprecated, or superseded states.

Inputs & outputs

You give it
Technical problem or design proposal
You get back
A standardized Architecture Decision Record (ADR) file

When to use architecture-decision-records

  • →Documenting new framework adoption
  • →Recording database technology choices
  • →Establishing rationale for API patterns
  • →Onboarding team members with design history

About architecture-decision-records

Standardizes the documentation of architectural decisions using the MADR format. It manages the lifecycle of decisions, including context analysis, trade-off recording, and status updates.

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.

When not to use it

  • →For minor version upgrades or routine maintenance
  • →For documenting implementation details

Prerequisites

adr-tools

Limitations

  • →ADRs are not intended for tracking bug fixes
  • →Requires team discipline to maintain the index and status updates

How it compares

It standardizes decision-making history into a searchable, version-controlled repository, replacing informal or scattered design discussions.

Compared to similar skills

architecture-decision-records side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
architecture-decision-records (this skill)547moReviewBeginner
wiki-architect116moNo flagsAdvanced
smart-docs411moReviewIntermediate
codebase-documenter611moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

More by wshobson

View all by wshobson →

You might also like

wiki-architect

microsoft

Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.

1144

smart-docs

sopaco

AI-powered comprehensive codebase documentation generator. Analyzes project structure, identifies architecture patterns, creates C4 model diagrams, and generates professional technical documentation. Use when users need to document codebases, understand software architecture, create technical specs, or generate developer guides. Supports all programming languages. Alternative to Litho/deepwiki-rs that uses Claude Code subscription without external API costs.

422

codebase-documenter

mhattingpete

Generates comprehensive documentation explaining how a codebase works, including architecture, key components, data flow, and development guidelines. Use when user wants to understand unfamiliar code, create onboarding docs, document architecture, or explain how the system works.

613

c4-architecture-c4-architecture

sickn33

Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.

117

dagger-design-proposals

dagger

Write design proposals for Dagger features. Use when asked to draft, review, or iterate on Dagger design documents, RFCs, or proposals.

66

design-documentation

jasonkneen

Transform approved requirements into comprehensive technical designs. Define system architecture, component interactions, data models, and interfaces to create a blueprint for implementation.

16

Search skills

Search the agent skills registry