architecture-decision-records

Document architectural decisions with structured templates and lifecycle tracking.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/raksok/netherica --skill architecture-decision-records-raksok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/raksok/netherica/tree/main/.agents/skills/architecture-decision-records
Command: npx skills add https://github.com/raksok/netherica --skill architecture-decision-records-raksok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADRs capture the context, options considered, and rationale behind significant technical decisions, enabling traceability, governance, and smoother onboarding.

Core Features & Use Cases

  • Lightweight Template-driven ADRs for recording decisions across projects
  • ADR lifecycle tracking (Proposed -> Accepted -> Superseded/Deprecated)
  • Central index and references to related ADRs for governance
  • Onboarding support by documenting decisions and rationale for teams

Quick Start

Create your first ADR using the MADR-style template and add it to the index.

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 avoid knowledge loss on my team?

Document architectural decisions using a structured ADR template that captures context, options considered, and rationale behind technical choices to preserve context and prevent knowledge loss across teams.

What is the best way to track the lifecycle state of an architecture decision record?

Track the architecture decision record lifecycle through defined states: Proposed, Accepted, Superseded, or Deprecated. This lifecycle tracking ensures proper governance and updates decision status over time as projects evolve.

How do I create my first ADR using a MADR-style template?

Create your first ADR by applying the MADR-style template to document your decision, then add the entry to a central index that links related ADRs for governance. This establishes traceability across your software project.

Can architecture decision records support onboarding for new software engineering teams?

Architecture decision records support onboarding by documenting decisions and their rationale for new team members. This provides essential context about technology choices and design reviews, enabling smoother integration into software projects.

How do I link related architecture decisions for cross-project governance?

Link related architecture decisions using a central index that references connected ADRs. This governance structure maintains traceability across teams and projects, ensuring decision relationships remain visible over the lifecycle.