skills.rest
Sumeet138
Sumeet138COMMUNITY
Explore all skills by this author →
Website𝕏@SumitGond28GitHub

architecture-decision-records

Document architectural decisions with context, rationale, and status values.

1|Updated Apr 14, 2026
Search Tags:#architecture#templates#documentation#adr#governance#software-architecture#decision-record
One-click install
npx skills add https://github.com/Sumeet138/qwen-code-agents --skill architecture-decision-records-sumeet138
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/Sumeet138/qwen-code-agents/tree/main/plugins/documentation-generation/skills/architecture-decision-records
Command: npx skills add https://github.com/Sumeet138/qwen-code-agents --skill architecture-decision-records-sumeet138

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions are often made in silos and quickly forgotten, leading to inconsistent designs and costly rework over time.

Core Features & Use Cases

  • Structured templates to document context, decision, and consequences for significant technical choices.
  • Lifecycle management with statuses (Proposed, Accepted, Deprecated, Superseded, Rejected) to govern governance and traceability.
  • Clear guidance on organization, linking related ADRs, and maintaining a discoverable decision log.

Quick Start

Create an ADR for a major architectural decision using the standard template and include context, decision, and consequences.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema
What is an Architecture Decision Record and when do I need to document one?▼

An Architecture Decision Record (ADR) captures context, rationale, and consequences for significant technical choices. You need an ADR when making major technology selections, design pattern choices, or governance decisions across teams and lifecycle stages.

How do I document architectural decisions using an ADR template?▼

To document architectural decisions, create an ADR using a standard template that structures context, decision, and consequences. Assign a status value like Proposed, Accepted, or Rejected, then add it to a discoverable decision log index.

What statuses should I use to track the ADR lifecycle?▼

Track the ADR lifecycle using statuses: Proposed, Accepted, Deprecated, Superseded, and Rejected. These status values govern traceability and manage the evolution of architectural decisions over time.

How do I maintain a discoverable log of architecture decision records across teams?▼

Maintain a discoverable architecture decision log by creating an index of ADRs, linking related records together, and organizing them with clear guidance. This ensures decisions are accessible across teams and lifecycle stages.

Why does software architecture documentation often lead to inconsistent designs and rework?▼

Software architecture decisions often lead to rework when made in silos and quickly forgotten. Documenting with ADRs solves this by capturing context and consequences, ensuring consistent designs and traceable governance.

Related Skills

Explore More Software Engineering Skills→
alunduilalunduil
1

adr

Detect existing ADRs and scaffold new ones with correct numbering and structure.

Community
Intermediate
juliusljuliusl
1

implement-adr

Decompose ADRs into staged tasks and generate plan.md files with estimates.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

diagram-gen

Generate Mermaid diagrams for architecture, event flows, and sequence diagrams.

Community
Intermediate
mvandermeulenmvandermeulen
2

architecture-decision-records

Standardize creation and maintenance of Architecture Decision Records with predefined templates.

Community
Intermediate