architecture-decision-records

Name: architecture-decision-records
Availability: InStock
Author: s3nex-com

Create and manage Architecture Decision Records with a templated format.

Updated Apr 8, 2026

Search Tags:#architecture #templates #documentation #adr #governance #software-engineering #decision-record

Ready to run

npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill architecture-decision-records-s3nex-com

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/s3nex-com/sdlc-skills-library/tree/main/skills/phase1/architecture-decision-records
Command: npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill architecture-decision-records-s3nex-com

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADRs capture the rationale behind architectural choices, preserve institutional memory, and prevent knowledge drift across teams and time. They support onboarding, governance, and audits by making decisions explicit and traceable.

Core Features & Use Cases

Create, review, and maintain Architecture Decision Records (ADRs) with a consistent, templated format across the SDLC.
Maintain a searchable ADR index and references to templates and examples to support governance and onboarding.
Enforce ownership, status, and review cycles to ensure timely reevaluation and alignment with architectural principles.

Quick Start

Write an ADR for a current architectural decision using the ADR template and save it to docs/adr/ with a descriptive, kebab-case filename.

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 to prevent knowledge drift across teams?▼

Document architectural decisions using Architecture Decision Records (ADRs) to capture context, alternatives, and consequences. ADRs preserve institutional memory by making technology choices explicit and traceable across SDLC phases and domain tracks.

What fields should an ADR template include for software engineering governance?▼

An ADR template should include context, decision, alternatives, consequences, owner, and review date fields. Enforcing these fields ensures architectural decisions maintain ownership, status tracking, and scheduled reevaluation cycles for governance compliance.

How do I create and store architecture decision records with a consistent naming scheme?▼

Create ADRs using a templated format and save them under a docs/adr directory with descriptive, kebab-case filenames. This consistent file-naming scheme maintains a searchable ADR index for onboarding and audit support.

When do I need architecture decision records in the SDLC?▼

You need ADRs when teams make architectural choices affecting system architecture, technology selection, or governance across SDLC phases. They support onboarding, audits, and alignment by making the rationale behind decisions explicit and traceable.

Does this approach work for managing architectural decisions across multiple domain tracks?▼

Yes, ADRs apply to teams documenting decisions across multiple domain tracks and SDLC phases. The templated format enforces ownership, status, and review cycles to ensure timely reevaluation and alignment with architectural principles.

What is the best way to maintain a searchable ADR index for onboarding and governance?▼

The best way to maintain a searchable ADR index is storing records under docs/adr with consistent kebab-case filenames and templated fields. References to templates and examples support governance, onboarding, and audit traceability.