create-architectural-decision-record

Generate Architectural Decision Records with YAML frontmatter and markdown body.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/markarnoldutah/RVS --skill create-architectural-decision-record-markarnoldutah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-architectural-decision-record
Source: https://github.com/markarnoldutah/RVS/tree/main/.github/skills/create-architectural-decision-record
Command: npx skills add https://github.com/markarnoldutah/RVS --skill create-architectural-decision-record-markarnoldutah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of Architectural Decision Records (ADRs) to ensure clear, consistent, and AI-consumable documentation of key architectural choices.

Core Features & Use Cases

  • Structured ADR Generation: Creates ADRs following a standardized format with YAML frontmatter and specific sections for context, decision, consequences, and alternatives.
  • AI-Optimized Formatting: Ensures documents are readable by both humans and machines.
  • Use Case: When deciding on a new database technology, use this Skill to document the problem, the chosen solution, its pros and cons, and the alternatives considered, ensuring all stakeholders have a clear record.

Quick Start

Use the create-architectural-decision-record skill to create an ADR for the decision 'Implement a new caching layer' with the context 'Our application is experiencing high latency under load'.

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 AI consumption?

You can document architectural decisions by generating ADRs with structured YAML frontmatter and markdown bodies, ensuring the technical context and consequences are readable by both humans and AI.

What is an Architectural Decision Record and when should I use one?

An Architectural Decision Record (ADR) documents a key technical choice, including its context, alternatives, and consequences. You should use an ADR whenever you make a significant architectural decision that impacts stakeholders.

How do I generate an ADR for a new database technology decision?

To generate an ADR for a database technology, provide the decision context and chosen solution. The output structures the problem, alternatives, and consequences into a standardized markdown format for clear stakeholder review.

What is the best way to format technical documentation for machine parsing?

The best way to format technical documentation for machine parsing is using a standardized ADR structure with YAML frontmatter, which separates metadata from the markdown body to optimize readability for automated systems.

Can I use an ADR format to document caching layer implementations?

Yes, you can use an ADR format to document caching layer implementations. It captures the latency context, the chosen caching solution, and the trade-offs, ensuring all stakeholders have a clear technical record.

Does generating ADRs require specific dependencies or components?

No, generating ADRs with this Skill requires no specific dependencies or components. It directly outputs structured YAML frontmatter and markdown text based on the architectural context and decision you provide.