architecture-decision-records

Create and manage Architecture Decision Records with MADR-style templates and adr-tools automation.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Himanshu040604/codex-skills-setup --skill architecture-decision-records-himanshu040604
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/Himanshu040604/codex-skills-setup/tree/main/assets/codex/skills/claude-import/skills/plugins/documentation-generation%40claude-code-workflows/skills/architecture-decision-records
Command: npx skills add https://github.com/Himanshu040604/codex-skills-setup --skill architecture-decision-records-himanshu040604

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires adr-tools, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams systematically document and manage significant technical decisions, ensuring clarity, consistency, and historical context for architectural choices.

Core Features & Use Cases

  • ADR Creation: Generate Architecture Decision Records (ADRs) using various templates (Standard, Lightweight, Y-Statement, Deprecation, RFC).
  • ADR Management: Organize ADRs within a structured directory, maintain an index, and track their lifecycle (Proposed, Accepted, Deprecated, Superseded).
  • Use Case: When your team decides to adopt a new database technology, use this Skill to create an ADR detailing the context, decision drivers, considered options, the final decision, and its consequences.

Quick Start

Use the architecture-decision-records skill to create a new ADR for adopting TypeScript.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema
How do I document architecture decisions for my engineering team?

You document architecture decisions by creating Architecture Decision Records (ADRs) that capture context, decision drivers, considered options, and consequences. This Skill automates ADR creation using multiple templates like MADR, lightweight, Y-statement, and RFC formats.

What templates can I use for creating technical decision records?

Available technical decision record templates include Standard MADR, lightweight, Y-statement, deprecation, and RFC formats. Each template structures architectural choices differently to accommodate various documentation needs and team preferences.

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

Manage ADR lifecycles by organizing records in a structured directory, maintaining an index, and tracking status changes from Proposed to Accepted, Deprecated, or Superseded. The Skill uses adr-tools for lifecycle automation and review processes.

Does this ADR tool require adr-tools to generate decision records?

Yes, adr-tools is required as a dependency to automate the creation and maintenance of Architecture Decision Records. It enables directory organization, indexing, and lifecycle management for your technical decisions.

When should I use a deprecation template versus a standard ADR?

Use a deprecation template when marking a previously accepted architectural decision as obsolete or replaced. Use a standard MADR template for new proposals, documenting context, decision drivers, considered options, and consequences.

What is the best way to track superseded architectural decisions?

Track superseded architectural decisions by updating the ADR lifecycle status and maintaining a structured directory index. This Skill supports lifecycle management to ensure historical context remains accessible when decisions are replaced.