create-adr

Create Architecture Decision Records with ADR-NNN naming and lifecycle statuses.

3|Updated Nov 28, 2025

Search Tags:#architecture #documentation #ADR #trade-offs #decision-records

Ready to run

npx skills add https://github.com/rayk/lucid-toolkit --skill create-adr-rayk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-adr
Source: https://github.com/rayk/lucid-toolkit/tree/main/plugins/architect/skills/create-adr
Command: npx skills add https://github.com/rayk/lucid-toolkit --skill create-adr-rayk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Create Architecture Decision Records (ADRs) following LCA conventions. INVOKE THIS SKILL when documenting decisions, capturing trade-offs, or updating history.

Core Features & Use Cases

ADR numbering, status, and dating
Context, drivers, options, chosen solution, and consequences
Links to related architecture docs and ADRs

Quick Start

adr-001-{slug}.md with a concise rationale and trade-offs

Frequently Asked Questions about create-adr

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

FAQPage Schema

What is an Architecture Decision Record and why do I need one?▼

An Architecture Decision Record (ADR) documents architectural decisions with context, trade-offs, and rationale in a standardized format. ADRs create a traceable history of why design choices were made, helping teams understand decision drivers and consequences over time.

How do I create and number Architecture Decision Records?▼

Create ADRs using the naming convention adr-NNN-{slug}.md with sequential 3-digit numbers starting at 001. Use the standardized template: Context, Drivers, Options, Decision Outcome, Consequences, and Links to related documents.

What statuses and lifecycle stages do ADRs support?▼

ADRs enforce standardized lifecycle statuses to track decision states through their history. This enables teams to mark decisions as proposed, accepted, superseded, or deprecated while maintaining an append-only record.

Can I link ADRs to other architecture documents and decisions?▼

Yes, ADRs include a Links section for referencing related architecture documents and other ADRs. This creates traceability across your decision history and connects architectural decisions to broader documentation.

Do ADRs follow a specific template format?▼

ADRs follow LCA conventions with a standardized template covering Context (the issue), Drivers (constraints and goals), Options (alternatives considered), Decision Outcome (chosen solution), Consequences (impacts), and Links to related decisions.

What happens when I need to update or supersede an existing ADR?▼

The append-only history requirement means you create a new ADR that references and supersedes the previous one, preserving the full decision history. This maintains traceability and shows how architectural thinking evolved.