arch:create-adr

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of Architecture Decision Records (ADRs) in the MADR format, ensuring that critical architectural choices are well-documented and their rationale is preserved.

Core Features & Use Cases

  • Automated ADR Generation: Creates ADRs based on story context, Non-Functional Requirements (NFRs), and technical context.
  • MADR Format Compliance: Generates ADRs adhering to the MADR standard, including status, date, decision-makers, context, drivers, options, outcome, and implementation notes.
  • Auto-Numbering: Sequentially numbers new ADRs based on existing documentation.
  • Use Case: When a new feature requires integrating a new AWS service like DynamoDB, this Skill analyzes the story details and NFRs to generate a comprehensive ADR outlining the decision to use DynamoDB, its alternatives, and implementation considerations.

Quick Start

Use the arch:create-adr skill to generate a new Architecture Decision Record for the current story.

Frequently Asked Questions about arch:create-adr

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

FAQPage Schema
How do I generate an Architecture Decision Record automatically?

This Skill generates an Architecture Decision Record automatically by analyzing story context, NFRs, and technical details to produce a structured document with options and implementation notes.

What is the MADR format for architecture documentation?

The MADR format is a structured standard for architecture documentation that includes status, date, decision-makers, context, drivers, options, outcome, and implementation notes to preserve decision rationale.

How do I document AWS architectural decisions like DynamoDB integration?

Document AWS architectural decisions by processing story details and non-functional requirements to outline the chosen service, alternatives, and specific implementation considerations for your feature.

How do I auto-number Architecture Decision Records in a project?

Auto-number Architecture Decision Records by scanning existing documentation and sequentially assigning numbers to new records generated from your current development story context.

Can I integrate ADR generation into an existing development workflow?

You can integrate ADR generation into development workflows to support tracking and implementation, automatically generating documentation from story context as architectural decisions are made.

What context is needed to create a decision record for non-functional requirements?

Creating a decision record for non-functional requirements requires story context and technical details to populate the MADR format, ensuring architectural drivers and outcomes are fully documented.