architecture-decision-records

Create and manage Architecture Decision Records in multiple formats.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/TriNgo0108/z-command --skill architecture-decision-records-tringo0108
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/TriNgo0108/z-command/tree/main/templates/skills/architecture-decision-records
Command: npx skills add https://github.com/TriNgo0108/z-command --skill architecture-decision-records-tringo0108

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured and consistent way to document significant technical decisions, ensuring clarity, rationale, and consequences are captured for current and future reference.

Core Features & Use Cases

  • Standardized ADR Creation: Utilizes various templates (MADR, Lightweight, Y-Statement, Deprecation, RFC) to suit different decision documentation needs.
  • ADR Lifecycle Management: Guides users through proposing, accepting, deprecating, and superseding decisions.
  • Use Case: When deciding on a new database technology, use this Skill to create an Architecture Decision Record (ADR) that outlines the context, considered options, the final decision, and its implications.

Quick Start

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

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 technical decisions using Architecture Decision Records?

You create an Architecture Decision Record by utilizing templates like MADR, Lightweight, Y-Statement, Deprecation, or RFC. This Skill facilitates generating these ADRs and managing their lifecycle, capturing context, options, and consequences for technical decisions.

What is the MADR format for technical decision documentation?

MADR is one of multiple Architecture Decision Record formats supported for technical decision documentation. It provides a structured template to outline context, considered options, the final decision, and implications, ensuring clarity and rationale are captured for significant technical choices.

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

Managing an Architecture Decision Record lifecycle involves guiding decisions through proposing, accepting, deprecating, and superseding stages. This Skill supports lifecycle management to maintain accurate historical context as technical decisions evolve within the docs/adr/ directory.

Does this ADR creation process require adr-tools to generate records?

Yes, the Architecture Decision Record creation process integrates with adr-tools for automated generation and management. This dependency allows the Skill to systematically structure and output ADR files within a designated docs/adr/ directory structure.

When should I use a Y-Statement or RFC template for an architecture decision?

Use Y-Statement or RFC Architecture Decision Record templates to suit different decision documentation needs based on complexity. The Skill supports these formats alongside MADR, Lightweight, and Deprecation styles to match the specific rationale and context requirements of your technical choices.

What is the best way to structure ADR files in my repository?

The best way to structure Architecture Decision Record files is within a dedicated docs/adr/ directory. This Skill integrates with adr-tools to automate generation and management, maintaining a consistent directory structure for all technical decision documentation.