create-adr

Generate Architecture Decision Records in MADR format from story context and NFRs.

2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/amdmax/claude_marketplace --skill create-adr-amdmax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-adr
Source: https://github.com/amdmax/claude_marketplace/tree/main/.claude/skills/create-adr
Command: npx skills add https://github.com/amdmax/claude_marketplace --skill create-adr-amdmax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of Architecture Decision Records (ADRs) in the MADR format, ensuring consistent documentation of architectural choices and their rationale.

Core Features & Use Cases

  • Automated Numbering: Automatically assigns sequential numbers to new ADRs.
  • Contextual Analysis: Analyzes story context, Non-Functional Requirements (NFRs), and technical constraints to inform ADR content.
  • MADR Format Generation: Creates ADRs adhering to the standard MADR template, including context, decision drivers, options, and outcomes.
  • Use Case: When a new feature requires selecting a database technology, this Skill can analyze the project's performance and security NFRs, present options like PostgreSQL vs. DynamoDB, document the chosen solution, and link it back to the original story.

Quick Start

Use the create-adr skill to generate a new Architecture Decision Record based on the current story context.

Frequently Asked Questions about create-adr

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

FAQPage Schema
How do I generate an Architecture Decision Record from story context?

To generate an Architecture Decision Record, this Skill analyzes story context, NFRs, and technical details to output a MADR format document. It automates ADR numbering, extracts decision drivers, identifies options, and documents the chosen outcome with implementation notes.

What is the MADR format for architecture decision records?

The MADR format structures architecture decision records by documenting context, decision drivers, considered options, and the chosen outcome. This Skill automatically generates ADRs adhering to this standard template to ensure consistent documentation of architectural choices and rationale.

How do I document technical governance decisions for non-functional requirements?

Document technical governance decisions by analyzing non-functional requirements and technical constraints to inform ADR content. This Skill automatically extracts decision drivers from NFRs, presents viable options, and records the final architectural outcome with linked implementation notes.

Does the create-adr skill support automated ADR numbering?

Yes, automated ADR numbering is supported. The Skill automatically assigns sequential numbers to new architecture decision records during generation, ensuring consistent tracking and linking back to the original story context for architectural governance.

When should I use architecture decision records in software engineering?

Use architecture decision records when a new feature requires selecting a technology or making an architectural choice. This Skill analyzes project performance and security NFRs, presents options like PostgreSQL versus DynamoDB, and documents the chosen solution to support knowledge sharing.

Can I analyze technical constraints and extract decision drivers automatically?

Yes, you can automatically extract decision drivers from technical constraints. The Skill performs contextual analysis on story context and NFRs to identify decision drivers, generate available options, and document the chosen outcome with implementation notes.