skills.rest
vrcms
vrcmsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-decision-records

Capture and maintain architectural decision records in standardized markdown format.

1|Updated Apr 6, 2026
Search Tags:#architecture#documentation#adr#best-practices#decision-making#software-design
One-click install
npx skills add https://github.com/vrcms/everything-qwen-code --skill architecture-decision-records-vrcms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/vrcms/everything-qwen-code/tree/main/.qwen/skills/architecture-decision-records
Command: npx skills add https://github.com/vrcms/everything-qwen-code --skill architecture-decision-records-vrcms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of architectural knowledge loss by ensuring that critical design decisions are documented, contextualized, and stored alongside the codebase rather than being lost in ephemeral communication channels.

Core Features & Use Cases

  • Structured Documentation: Automatically generates ADRs using the industry-standard Michael Nygard format.
  • Decision Tracking: Monitors conversations to detect when significant architectural trade-offs are being made and prompts for documentation.
  • Knowledge Retrieval: Allows developers to query the history of the project to understand the rationale behind specific technology or design choices.

Quick Start

Ask the assistant to record an architecture decision record for the current database migration strategy.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema
How do I document architecture decisions to preserve design rationale in my codebase?▼

Architecture decision records (ADRs) are structured markdown documents that capture technology choices, trade-offs, and alternatives. They are needed whenever significant architectural changes occur to preserve project history and design rationale.

How do I create an architecture decision record using the Michael Nygard format?▼

You generate an architecture decision record by asking the assistant to document a specific design trade-off, such as a database migration strategy. The system then outputs a standardized markdown file capturing the context, decision, and consequences.

Can I query past architecture decisions to understand why a specific technology was chosen?▼

Yes, you can retrieve past architecture decision records to understand the rationale behind specific technology choices. This knowledge retrieval mechanism allows developers to query project history and review the trade-offs of previous decisions.

How do I track architectural decisions made during software development sessions?▼

You track architectural decisions by monitoring development sessions to detect when significant trade-offs are made. The system then prompts you to document these choices, ensuring all significant changes are captured in standardized markdown.

Related Skills

Explore More Software Engineering Skills→
carson-sweetcarson-sweet
6

Manage Decisions

Record and track software architecture decisions in a project repository.

Community
Intermediate
broomvabroomva
3

decision-log

Document project decisions with context, alternatives, and rationale in Markdown.

Community
Intermediate
nesihaver-ILnesihaver-IL

update-docs

Update README, API, architecture docs, and changelogs after code changes.

Community
Intermediate
AmidVoshakulAmidVoshakul

architecture-decision-records

Standardize creation and maintenance of Architecture Decision Records with templates.

Community
Intermediate