create-architectural-decision-record

Generate standardized Architectural Decision Record documents with front matter and structured sections.

1|Updated Feb 23, 2026

Search Tags:#architecture #decision making #documentation #software design #adr #technical documentation

Ready to run

npx skills add https://github.com/Gabeujin/workspace-init-mcp --skill create-architectural-decision-record-gabeujin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-architectural-decision-record
Source: https://github.com/Gabeujin/workspace-init-mcp/tree/main/awesome/skills/create-architectural-decision-record
Command: npx skills add https://github.com/Gabeujin/workspace-init-mcp --skill create-architectural-decision-record-gabeujin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of Architectural Decision Records (ADRs), ensuring that critical architectural choices are documented clearly, consistently, and in a format optimized for both human understanding and AI processing.

Core Features & Use Cases

Structured ADR Generation: Creates ADR documents following a standardized format with front matter and specific sections (Context, Decision, Consequences, Alternatives, etc.).
AI-Optimized Formatting: Uses precise language and coded bullet points for machine readability.
Use Case: When deciding on a new database technology, use this Skill to generate a comprehensive ADR that details the problem, the chosen solution, the alternatives considered (and why they were rejected), and the potential positive and negative consequences.

Quick Start

Use the create-architectural-decision-record skill to create an ADR for the decision titled 'Implement Caching Layer'.

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 document architectural decisions for my software design?▼

You document architectural decisions by generating an Architectural Decision Record (ADR) that captures the context, chosen decision, alternatives, and stakeholders to ensure critical software design choices are recorded consistently.

What is the best format for an ADR to ensure technical documentation is machine readable?▼

An ADR format optimized for machine readability uses a standardized structure with front matter, specific sections for context and consequences, and coded bullet points to ensure precise language for AI processing.

How do I structure an ADR to include alternatives and consequences effectively?▼

You structure an ADR using standardized sections for Context, Decision, Consequences, and Alternatives, employing coded bullet points to clearly detail rejected options and the impact of the chosen architectural decision.

Where are generated Architectural Decision Records saved and how are they numbered?▼

Generated ADRs are saved in the `/docs/adr/` directory, automatically named using sequential numbering and a title slug to maintain an organized and traceable technical documentation history.

Do I need to manually format technical documentation when generating an ADR?▼

No, manual formatting is unnecessary because the ADR generation automatically applies a standardized format with front matter and structured sections for consequences and alternatives, ensuring consistent technical documentation.