create-adr

Generate MADR-format Architecture Decision Records with sequential numbering and YAML frontmatter.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/amak07/acr-automotive --skill create-adr-amak07
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-adr
Source: https://github.com/amak07/acr-automotive/tree/main/.claude/skills/create-adr
Command: npx skills add https://github.com/amak07/acr-automotive --skill create-adr-amak07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams record architectural decisions in MADR format, ensuring decisions are traceable and reproducible.

Core Features & Use Cases

  • MADR Template Adherence: Use the MADR structure.
  • Sequential ADR Numbering: Determine the next ADR number from docs/decisions/.
  • Documentation Output: Writes to docs/decisions/NNNN-[kebab-case-title].md.
  • Use Case: Record the choice to adopt Supabase for data storage.

Quick Start

Create an ADR for a new caching strategy and output to the appropriate docs/decisions file.

Frequently Asked Questions about create-adr

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

FAQPage Schema
How do I create an architecture decision record in MADR format?

MADR (Markdown Architecture Decision Records) is a structured format for documenting architectural decisions. This Skill generates MADR-compliant records by applying the standard template, determining the next sequential ADR number, and writing the file to docs/decisions/ with proper naming and YAML frontmatter for full standards compliance.

What's the correct way to number and organize ADR files in my project?

ADR files follow sequential numbering as NNNN-[kebab-case-title].md and are stored in docs/decisions/. This Skill automatically determines the next available number from existing ADRs, ensuring no gaps and preventing conflicts when multiple team members create records simultaneously.

Can I use MADR to document technology choices like database selection?

Yes. MADR is designed to capture technology decisions—such as adopting Supabase for data storage or choosing a new caching strategy—with full context on alternatives, consequences, and decision rationale. The Skill generates properly formatted records that make these choices traceable and reproducible.

Why should my team use architecture decision records?

Architecture decision records preserve the reasoning behind technical choices, making decisions traceable for future team members and preventing repeated debates. MADR's structured template ensures consistency and captures alternatives and consequences, reducing onboarding friction and supporting long-term system understanding.

Do I need to manually track ADR numbers, or does this handle it automatically?

This Skill automates ADR numbering by scanning docs/decisions/ for existing records and calculating the next sequential number, eliminating manual tracking and preventing numbering conflicts across your team's workflow.