skills.rest
hieuck
hieuckCOMMUNITY
Explore all skills by this author →
GitHub

architecture-decision-records

Capture architectural decisions as structured ADR documents under docs/adr.

Updated Mar 21, 2026
Search Tags:#workflow#architecture#versioning#documentation#adr#coding#decision-record
One-click install
npx skills add https://github.com/hieuck/Pro5ChromeManager --skill architecture-decision-records-hieuck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/hieuck/Pro5ChromeManager/tree/main/skills/architecture-decision-records
Command: npx skills add https://github.com/hieuck/Pro5ChromeManager --skill architecture-decision-records-hieuck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions are often scattered across chat, PRs, and personal notes. This skill provides a structured, versioned ADR format that lives with the codebase to preserve rationale over time.

Core Features & Use Cases

  • ADR format: lightweight, present-tense ADR documents that capture context, decisions, and consequences.
  • Lifecycle & indexing: supports proposed → accepted → deprecated/superseded, with an index for quick navigation.
  • Workflow integration: enables creating, reading, and updating ADRs alongside code in docs/adr.

Quick Start

Create an ADR when a significant architectural decision arises and document the context, options, and consequences using the ADR format.

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 architectural decisions in my codebase?▼

You should document architectural decisions by creating structured ADR documents that capture context, decisions, and consequences, storing them under docs/adr within your codebase.

What is the ADR lifecycle for managing decision records?▼

The ADR lifecycle manages decision records through stages: proposed, accepted, deprecated, or superseded. This lifecycle ensures decisions are tracked and updated as architectural trade-offs evolve over time.

When should I create an architecture decision record?▼

You should create an architecture decision record when a significant architectural decision arises during coding, planning, or review, specifically when meaningful trade-offs are discussed and need documented rationale.

Can I use templates and an index for architecture decision records?▼

Yes, the workflow supports lightweight ADR templates for consistent documentation and an ADR index for quick navigation, allowing you to efficiently create, read, and update decision records alongside your code.

What is the best way to version architectural decisions with code?▼

The best way to version architectural decisions is to store structured ADR documents directly in the docs/adr directory, ensuring decision rationale is versioned and lives with the codebase changes.

Related Skills

Explore More Software Engineering Skills→
emaarcoemaarco
3

create-adr

Create MADR-format Architectural Decision Records in the docs/adr/ directory.

Community
Intermediate
cescraflicescrafli

architecture-decision-records

Capture architectural decisions as structured ADR documents with context and alternatives.

Community
Advanced
GGEduGGEdu

architecture-decision-records

Document architectural decisions as ADRs with templates and lifecycle states.

Community
Advanced
PriyanshKuniyalPriyanshKuniyal

architecture-decision-records

Document and manage architectural decision records with templates and lifecycle statuses.

Community
Advanced