create-adr

Name: create-adr
Availability: InStock
Author: aSafeLobotomy

Create versioned ADR files with required metadata under docs/adr.

7|2|Updated Dec 14, 2025

Search Tags:#architecture #software engineering #documentation #adr #decision records #project governance #design decisions

Ready to run

npx skills add https://github.com/asafelobotomy/iCloud-Drive-Downloader --skill create-adr-asafelobotomy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-adr
Source: https://github.com/asafelobotomy/iCloud-Drive-Downloader/tree/main/.github/skills/create-adr
Command: npx skills add https://github.com/asafelobotomy/iCloud-Drive-Downloader --skill create-adr-asafelobotomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you document significant architectural and technology decisions so future maintainers can understand why choices were made and avoid re-litigating them.

Core Features & Use Cases

Structured ADR creation: Generates an Architectural Decision Record with consistent fields for context, decision, consequences, and alternatives.
Next-sequence file management: Automatically determines the next ADR number from existing files under docs/adr and writes a correctly named ADR file.
Decision capture workflow: Guides you to provide a decision title, context, rationale, alternatives, and stakeholders, then persists the result in a standard template for long-term reference.

Quick Start

Ask the Skill to create an ADR for your most important recent design decision, including the context, chosen approach, and the alternatives you considered.

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 Architectural Decision Record for a software design choice?▼

To create an Architectural Decision Record, you provide a title, context, rationale, alternatives, and stakeholders. The system validates these inputs and writes a versioned, template-based ADR file to preserve context for significant design decisions.

What should be included in an ADR to document project governance decisions?▼

An ADR for project governance should include context, the accepted decision, consequences, rejected alternatives, and stakeholders. This structured documentation ensures future maintainers understand why specific technology choices were made and can avoid re-litigating them.

How are ADR files numbered and organized in a repository?▼

ADR files are organized under the docs/adr directory. The system automatically determines the next sequence number from existing files and writes a correctly named markdown file following the adr-NNNN-title-slug.md format for consistent versioning.

Can I document rejected and superseded design options in an ADR?▼

Yes, you can record accepted, rejected, or superseded options during software architecture decision-making. Capturing these alternatives ensures future teams understand the full scope of evaluated choices and the reasoning behind the final decision.

What is the best way to maintain context for significant software engineering decisions?▼

The best way to maintain context is generating a versioned ADR file with required metadata. This captures key design choices, validates essential inputs before writing, and produces a standard template for long-term reference in software engineering projects.

Do I need to manually format the markdown file when recording architectural decisions?▼

No, you do not need to manually format the markdown file. The system applies a standard template for long-term reference, automatically handling the file naming sequence and validating that all essential inputs are provided before writing the document.