skills.rest
wesleyegberto
wesleyegbertoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-decision-records

Document architectural decisions as structured ADR files under docs/adr.

3|2|Updated Mar 23, 2026
Search Tags:#architecture#documentation#adr#traceability#rationale#decision-record
One-click install
npx skills add https://github.com/wesleyegberto/software-engineering-skills --skill architecture-decision-records-wesleyegberto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/wesleyegberto/software-engineering-skills/tree/main/plugins/architecture/skills/architecture-decision-records
Command: npx skills add https://github.com/wesleyegberto/software-engineering-skills --skill architecture-decision-records-wesleyegberto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADRs are scattered across conversations, PRs, and memory; this skill provides a lightweight, codified way to capture architectural decisions as living documents.

Core Features & Use Cases

  • Capture decision context, alternatives considered, and rationale at the moment of decision to ensure future traceability.
  • Maintain a centralized ADR log under docs/adr with an index for quick lookup.
  • Generate consistent ADR documents that guide future implementations and governance.

Quick Start

Detect a decision moment and create a new ADR document with context, decision, and alternatives.

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 during coding sessions?▼

To document architectural decisions during coding sessions, you generate structured ADR documents capturing context, alternatives, rationale, and consequences, storing them under docs/adr for future traceability.

What is the lightweight ADR format for capturing decision rationale?▼

The lightweight ADR format consists of title, date, status, context, decision, alternatives, and consequences. It provides a standardized structure to ensure architectural decisions are readable and traceable for future developers.

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

You manage the lifecycle of an architecture decision record by tracking its status through defined stages: proposed, accepted, deprecated, and superseded, ensuring the decision log remains an accurate living history.

What's the best way to maintain a centralized log of architectural decisions?▼

The best way to maintain a centralized log of architectural decisions is to store ADR documents under docs/adr with an index, allowing quick lookup and consistent governance of past technical choices.

Can I capture architectural alternatives and consequences without a heavy documentation tool?▼

Yes, you can capture architectural alternatives and consequences without a heavy tool by using a lightweight ADR format that records context and rationale at the moment of decision directly within your project files.

Related Skills

Explore More Software Engineering Skills→
xxihxxih
1

architecture-decision-records

Capture architecture decisions as structured ADR documents in docs/adr.

Community
Intermediate
bossjonesbossjones
1

setup-matt-pocock-skills

Configure issue trackers, triage labels, and domain documentation for engineering skills.

Community
Advanced
packetalienpacketalien

create-stories

Break epics into implementable stories from GDD, ADRs, and control manifests.

Community
Advanced
shin0720shin0720

auto-why

Retrieve decision rationale from Lore, SPEC, and ARCHITECTURE documentation.

Community
Basic