skills.rest
Movchanets
MovchanetsCOMMUNITY
Explore all skills by this author →
GitHub

architecture-decision-records

Capture and structure architecture decision records with context, options, and consequences.

Updated May 5, 2026
Search Tags:#architecture#documentation#adr#governance#software-engineering#tradeoffs#decision-records
One-click install
npx skills add https://github.com/Movchanets/Microservices_Learning --skill architecture-decision-records-movchanets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/Movchanets/Microservices_Learning/tree/main/.agents/skills/architecture-decision-records
Command: npx skills add https://github.com/Movchanets/Microservices_Learning --skill architecture-decision-records-movchanets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams capture significant technical decisions in a durable, reviewable format so future readers can understand what was decided, why it was chosen, and what trade-offs were accepted.

Core Features & Use Cases

  • Decision Capture: Record the context, options, rationale, and consequences behind major architecture choices.
  • Lifecycle Management: Track ADR status over time, including proposed, accepted, deprecated, superseded, and rejected outcomes.
  • Use Case: Use it when selecting databases, API gateways, integration patterns, or security approaches for a service or platform.

Quick Start

Ask the AI to draft an ADR for your decision, including context, considered options, the final choice, consequences, and current status.

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 software architecture decisions for my team?▼

Architecture Decision Records (ADRs) provide a durable, reviewable format to document significant technical decisions, ensuring future readers understand what was decided, why it was chosen, and what trade-offs were accepted.

What should be included in an architecture decision record template?▼

An effective architecture decision record template should capture context, considered options, the final choice, consequences, rationale, and lifecycle status to provide comprehensive decision governance for software teams.

When should I create an architecture decision record?▼

Create an ADR when selecting databases, API gateways, integration patterns, or security approaches for a service or platform, capturing major architecture choices in a durable, reviewable format for historical review and onboarding.

How do I manage the lifecycle status of architecture decision records?▼

Track architecture decision records by updating their lifecycle status over time, including proposed, accepted, deprecated, superseded, and rejected outcomes, to maintain accurate historical review and decision governance.

What is the best way to capture trade-off analysis for technology selection?▼

Capture trade-off analysis by structuring ADRs with context, considered options, final choice, and accepted consequences, providing a structured format for technology selection and decision governance.

Can architecture decision records be used for onboarding new team members?▼

ADRs support onboarding by documenting the context, rationale, and trade-offs behind major architecture choices, allowing new team members to review historical decisions and understand why specific technologies were selected.

Related Skills

Explore More Software Engineering Skills→
spencerpaulyspencerpauly
672

architecture-decision-records

Document significant technical decisions as architecture decision records with context and rationale.

Community
Intermediate
ekremmkasapekremmkasap

architecture-decision-records

Document architecture decisions with standardized ADR templates and lifecycle tracking.

Community
Advanced
ChrstprJohnChrstprJohn

architecture-decision-records

Document and manage Architecture Decision Records with Markdown templates and frontmatter metadata.

Community
Advanced
boomNDSboomNDS

architecture

Capture architectural decisions with ADR templates and rationale.

Community
Basic