skills.rest
pythoninthegrasses
pythoninthegrassesOFFICIAL
Explore all skills by this author →
GitHub

architecture-decision-records

Document architectural decision context, options, and rationale in standardized ADR format.

1|Updated Dec 16, 2025
Search Tags:#architecture#templates#documentation#adr#governance#software-architecture#decision-records
One-click install
npx skills add https://github.com/pythoninthegrasses/lunchjs --skill architecture-decision-records-pythoninthegrasses
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/pythoninthegrasses/lunchjs/tree/main/.claude/skills/architecture-decision-records
Command: npx skills add https://github.com/pythoninthegrasses/lunchjs --skill architecture-decision-records-pythoninthegrasses

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture Decision Records (ADRs) provide a structured way to capture context, options, decisions, and consequences for significant technical choices, improving traceability and onboarding.

Core Features & Use Cases

  • Standard templates and checklists to document decisions consistently.
  • Lifecycle tracking (Proposed, Accepted, Deprecated, Superseded) to reflect current status.
  • Onboarding support for new team members by presenting historical decisions and rationales.

Quick Start

Create a new ADR using the MADR template and store it under docs/adr with a descriptive title.

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 for software projects?▼

Document architectural decisions by capturing context, options, and consequences in a standardized Architecture Decision Record. This enforces consistent templates and lifecycle tracking to support future maintenance and onboarding.

What is the MADR template for architecture decision records?▼

The MADR template provides a standardized format for architecture decision records, applying structured checklists to document technology choices, system boundaries, and governance consistently across projects and teams.

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

Track architecture decision lifecycle status using states like Proposed, Accepted, Deprecated, and Superseded. This reflects the current standing of technical choices and maintains historical traceability for onboarding.

When should I use architecture decision records in software engineering?▼

Use architecture decision records when making significant technical choices about technology selections, system boundaries, or governance. They capture the rationale needed to support future maintenance and team onboarding.

Can I apply a standardized ADR format across multiple teams?▼

Yes, you can apply a standardized ADR format across multiple teams. The approach enforces consistent templates and lifecycle tracking for decisions, ensuring uniform documentation practices throughout an organization.

What should be included in an architecture decision record?▼

An architecture decision record should include the decision context, available options, the chosen decision, and its consequences. This structured rationale supports future maintenance and clarifies historical technical choices.

Related Skills

Explore More Software Engineering Skills→
asterkinasterkin
1

adr

Create Architecture Decision Records with standardized sections and automatic numbering.

Community
Basic
HomericIntelligenceHomericIntelligence
18

doc-generate-adr

Generate Architecture Decision Records with standardized templates and lifecycle statuses.

Official
Basic
xenitV1xenitV1
132

architecture

Systematize requirements analysis and ADR documentation for architecture decisions.

Community
Basic
bradtaylorsfbradtaylorsf
8

architecture-decisions

Generate Architecture Decision Records with a standardized template.

Community
Basic