architecture-decision-record

Generate structured Architecture Decision Records from design conversations.

47|2|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/Amazon-Quick/Amazon-Quick-official-catalog --skill architecture-decision-record-amazon-quick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-record
Source: https://github.com/Amazon-Quick/Amazon-Quick-official-catalog/tree/main/skills/architecture-decision-record
Command: npx skills add https://github.com/Amazon-Quick/Amazon-Quick-official-catalog --skill architecture-decision-record-amazon-quick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are often captured inconsistently, making it hard to trace rationale and outcomes over time. This Skill standardizes ADR creation by producing MADR or Nygard format documents from design conversations, meeting notes, or direct prompts, including context, decision drivers, options considered, and consequences.

Core Features & Use Cases

  • Generate fully structured Architecture Decision Records from conversations, transcripts, or prompts.
  • Support MADR and Nygard templates with versioning and status tracking.
  • Produce ready-to-commit Markdown ADR files with cross-links to related decisions.

Quick Start

Run with a decision title and context to create the next ADR and export it to the ADR directory.

Frequently Asked Questions about architecture-decision-record

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

FAQPage Schema
How do I generate an Architecture Decision Record from design discussion notes?

Generate Architecture Decision Records by providing design conversations, transcripts, or prompts to produce structured Markdown files capturing context, decision drivers, options considered, and consequences.

What is the difference between MADR and Nygard templates for decision records?

MADR and Nygard are two supported ADR template formats. MADR offers structured decision driver fields, while Nygard provides a minimalist format; both support sequential numbering, status tracking, and cross-linking superseded records.

How do I document architecture decisions during a project handoff?

Document architecture decisions during project handoffs by running the Skill with a decision title and context to create the next sequentially numbered ADR, capturing rationale and outcomes for traceability.

Can I track the status of superseded architecture decisions in Markdown?

Track superseded architecture decisions using built-in status tracking and cross-linking features that automatically connect old Markdown ADR files to new ones, maintaining a clear decision history.

When do I need to create ADR files for software architecture reviews?

Create ADR files during architecture reviews and design discussions when you need to standardize the capture of decision drivers, options considered, and consequences to ensure long-term rationale traceability.

What is the best way to standardize architecture documentation across multiple projects?

Standardize architecture documentation by generating ready-to-commit Markdown ADR files using consistent MADR or Nygard templates, ensuring sequential numbering and cross-links to related decisions across projects.