adr-authoring

Generate and validate Architecture Decision Records with structured templates.

1|Updated Jun 20, 2026

Search Tags:#architecture #documentation #adr #governance #trade-offs #decision-records

Ready to run

npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill adr-authoring-shafibabar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adr-authoring
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/adr-authoring
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill adr-authoring-shafibabar

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the problem of inconsistent, undocumented, or forgotten architectural decisions, preventing the costly re-litigation of settled choices and ensuring future engineers understand the reasoning behind the system's design.

Core Features & Use Cases

Structured ADR Generation: Provides a standardized template and automated scaffolding to ensure every decision captures context, options, rationale, and trade-offs.
Mechanical Validation: Includes automated scripts to verify that ADRs meet quality criteria, such as the presence of explicit trade-offs and consequence analysis.
Principle Management: Distinguishes between point-in-time decisions and durable architecture principles, ensuring general guidance is preserved even when specific decisions are superseded.

Quick Start

Run the scaffold script to generate a new architecture decision record for the classification service by providing the product name and a descriptive slug.

Frequently Asked Questions about adr-authoring

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

FAQPage Schema

What are Architecture Decision Records and when do I need to document them?▼

Architecture Decision Records capture design rationale and trade-offs for non-obvious, consequential, or cross-cutting architectural choices. You need them during the software design phase to prevent the costly re-litigation of settled choices and ensure future engineers understand system reasoning.

How do I standardize architectural decisions across my engineering team?▼

You can standardize architectural decisions by using a structured ADR template with automated scaffolding to capture context, options, rationale, and trade-offs. This ensures every decision record meets consistent quality criteria and supports structured supersession chains for long-term system evolution.

How do I generate a new architecture decision record for a specific service?▼

To generate an architecture decision record, run the scaffold script by providing the product name and a descriptive slug. This automatically creates a standardized document structure for capturing your design rationale and trade-offs.

Can I mechanically validate that my ADRs include explicit trade-offs and consequences?▼

Yes, automated scripts can mechanically validate ADRs to verify they meet quality criteria, such as the presence of explicit trade-offs and consequence analysis. This ensures your decision records maintain structural integrity and capture necessary design rationale.

How do I manage durable architecture principles versus point-in-time decisions?▼

You can manage durable architecture principles separately from point-in-time decisions using principle management features. This distinguishes general guidance from specific architectural choices, ensuring overarching rules are preserved even when individual decisions are superseded.

What are the limitations of relying on informal architectural documentation?▼

Informal architectural documentation often leads to inconsistent, undocumented, or forgotten decisions, which causes the costly re-litigation of settled choices. Without structured supersession chains, future engineers may fail to understand the reasoning behind the system's design.