create-architectural-decision-record

Generate standardized Architectural Decision Records in Markdown with front matter and structured sections.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/tamago0224/kuroshio-mta --skill create-architectural-decision-record-tamago0224
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-architectural-decision-record
Source: https://github.com/tamago0224/kuroshio-mta/tree/main/.agents/skills/create-architectural-decision-record
Command: npx skills add https://github.com/tamago0224/kuroshio-mta --skill create-architectural-decision-record-tamago0224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool automates the creation of standardized Architectural Decision Records (ADRs) to capture and communicate important design decisions for AI-augmented teams, ensuring consistent documentation across projects.

Core Features & Use Cases

  • Generates ADR Markdown with required front matter (title, status, date, authors, tags) and content sections (Context, Decision, Consequences, Alternatives with rationales, Implementation Notes, References)
  • Saves the ADR to the docs/adr directory following the naming convention adr-NNNN-[title-slug].md
  • Validates required inputs and produces machine-readable output suitable for repository governance and human review

Quick Start

Provide the ADR inputs (DecisionTitle, Context, Decision, Alternatives, Stakeholders) and request ADR generation.

Frequently Asked Questions about create-architectural-decision-record

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

FAQPage Schema
How do I generate an Architectural Decision Record in Markdown for my project?

To generate an Architectural Decision Record, provide the required inputs like DecisionTitle, Context, Decision, Alternatives, and Stakeholders. The tool outputs a standardized Markdown file with structured sections and front matter, saving it automatically to your docs/adr directory.

What is an ADR and what sections should it include for architecture planning?

An ADR is an Architectural Decision Record that captures important design choices. It should include front matter like title, status, date, authors, and tags, alongside content sections for Context, Decision, Consequences, Alternatives with rationales, Implementation Notes, and References.

Can I automatically save ADR documentation using a specific file naming convention?

Yes, ADR documentation can be automatically saved using the adr-NNNN-[title-slug].md naming convention. The tool handles the file creation and saves it directly under the /docs/adr/ folder for consistent repository governance and human review.

Does this ADR generator validate required inputs before creating the Markdown file?

Yes, the ADR generator validates required inputs before creating the Markdown file. It checks for necessary fields like Context, Decision, and Alternatives to ensure consistent, machine-readable output suitable for repository governance.

What is the best way to document AI-assisted architectural decisions consistently?

The best way to document AI-assisted architectural decisions consistently is using standardized ADR templates. This ensures every AI-driven choice is captured with machine-readable Markdown front matter and structured sections for human review.

Why does my ADR workflow need machine-readable output for repository governance?

Your ADR workflow needs machine-readable output for repository governance to automate compliance checks and track decision history. Standardized Markdown with structured front matter allows automated tools to parse and validate architectural decisions.