tech-arch-architecture-decision-records

Create and index Architecture Decision Records using MADR and other templates.

Updated Jan 28, 2026

Search Tags:#documentation #adr #governance #rfc #software-architecture #madr #architecture-decision-record

Ready to run

npx skills add https://github.com/scanady/nexus-agents --skill tech-arch-architecture-decision-records

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tech-arch-architecture-decision-records
Source: https://github.com/scanady/nexus-agents/tree/main/skills/tech-arch-architecture-decision-records
Command: npx skills add https://github.com/scanady/nexus-agents --skill tech-arch-architecture-decision-records

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions are often scattered, difficult to trace, and hard to onboard new engineers to historical choices. This skill provides a formal approach to creating, maintaining, and indexing Architecture Decision Records (ADRs) to improve governance, transparency, and long-term decision context.

Core Features & Use Cases

ADR templates: MADR (Standard), Lightweight, Y-Statement, Deprecation, and RFC-style templates for structured decision capture.
Governance & lifecycle: Guidelines to index ADRs, link related decisions, notify stakeholders, and track supersession.
Onboarding & auditing: Helps engineers understand past decisions and supports audits, retroactive analysis, and design governance.

Quick Start

Draft an ADR using the MADR template to capture a major architectural decision.

Frequently Asked Questions about tech-arch-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 should I document one?▼

An architecture decision record (ADR) captures significant software architecture choices to ensure traceability and governance. You should document an ADR when making major design decisions, recording trade-offs, or establishing formal governance processes across projects.

How do I write an ADR using the MADR template?▼

To write an ADR using the MADR template, draft your architectural decision by filling out the structured MADR format to capture context, decision drivers, considered options, and consequences. This ensures standardized documentation and governance for your project.

Does this approach support lightweight ADRs and RFC-style documentation?▼

Yes, the approach supports lightweight ADRs and RFC-style documentation alongside MADR, Y-Statement, and Deprecation templates. This allows you to capture architectural decisions at the appropriate level of formality for your specific governance needs.

How do I manage ADR lifecycle and link related architectural decisions?▼

You manage the ADR lifecycle by indexing records, linking related architectural decisions, notifying stakeholders, and tracking supersession. This governance workflow ensures historical context is preserved and engineers can trace how past decisions evolve over time.

What is the best way to onboard engineers to historical architectural decisions?▼

The best way to onboard engineers to historical architectural decisions is using indexed ADRs. Applying structured templates and governance workflows provides the traceability and historical context needed for retroactive analysis and auditing.

Can I use ADRs to track deprecation of architectural components?▼

Yes, you can use ADRs to track deprecation of architectural components by applying the Deprecation template. This records design trade-offs and formally documents the lifecycle phase of architectural components being phased out.