agent-adr-generator

Generate machine-readable Markdown Architectural Decision Records with structured metadata.

12|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill agent-adr-generator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-adr-generator
Source: https://github.com/Space-Dinosaurs/DinoStack/tree/main/.openclaw/skills/agent-adr-generator
Command: npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill agent-adr-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of Architectural Decision Records (ADRs) with a standardized structure, ensuring clear rationale and traceability.

Core Features & Use Cases

  • ADR creation workflow: Collect inputs (title, context, decision, alternatives, stakeholders) and compute ADR number.
  • Markdown ADR document: Produce ADR in the standard YAML front matter plus sections (Context, Decision, Consequences, Alternatives, References).
  • Documentation governance: Enforce sequential numbering, proper metadata, and repository placement in docs/adr/.

Quick Start

Provide inputs to start ADR generation and generate a new ADR document under docs/adr/

Frequently Asked Questions about agent-adr-generator

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

FAQPage Schema
How do I generate an Architectural Decision Record in Markdown?▼

Architectural Decision Records document major design decisions, trade-offs, and consequences across engineering teams. They enforce governance by providing a formal, traceable structure for recording context, alternatives, and the rationale behind significant software architecture choices.

What is the standard structure for an Architectural Decision Record?▼

To create an ADR document, provide the title, context, decision, alternatives, and stakeholders. The system computes the ADR number, applies front-matter metadata, and generates the complete Markdown file directly in your repository's docs/adr/ directory for immediate governance compliance.

How do I enforce consistent ADR numbering and metadata across repositories?▼

To enforce consistent ADR numbering and metadata across repositories, automate document generation with sequential ID computation and required front-matter fields. This ensures proper metadata formatting and repository placement without manual intervention.

When do I need to document architectural decisions with an ADR?▼

You need to document architectural decisions with an ADR when software architecture teams make major design decisions involving trade-offs and consequences. Recording the context, chosen decision, and alternatives ensures traceability and enforces governance across projects and engineering teams.