architecture-decision-records

Document architecture decisions with standardized ADR templates and lifecycle tracking.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ekremmkasap/jarvis --skill architecture-decision-records-ekremmkasap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/ekremmkasap/jarvis/tree/main/server/agent_prompts/wshobson/plugins/documentation-generation/skills/architecture-decision-records
Command: npx skills add https://github.com/ekremmkasap/jarvis --skill architecture-decision-records-ekremmkasap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions often lack traceability, leading to inconsistent designs and knowledge gaps across teams.

Core Features & Use Cases

  • Standard ADR templates (MADR Standard, Lightweight ADR, Y-Statement, Deprecation ADR, RFC Style) to document decisions.
  • ADR index and lifecycle management to track status, revisions, and superseding decisions.
  • Guided review processes and automation tips to improve governance and onboarding.

Quick Start

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

Frequently Asked Questions about 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 do I need one?

An Architecture Decision Record (ADR) captures architectural decisions and their rationales to ensure traceability. You need an ADR when making significant software design choices to prevent inconsistent designs and knowledge gaps across teams.

How do I document architecture decisions using standardized templates?

Document architecture decisions by applying standardized ADR templates like MADR Standard, Lightweight ADR, or Y-Statement. These templates help you consistently capture context, alternatives, trade-offs, and lifecycle events across projects.

What is the best way to track the lifecycle and status of architecture decisions?

The best way to track architecture decision lifecycle is using an ADR index to monitor status, revisions, and superseding decisions. This enables historical analysis, improves governance, and supports team onboarding.

Can I use a lightweight ADR format for smaller architectural decisions?

Yes, you can use the Lightweight ADR template for smaller architectural decisions. It provides a streamlined format to capture context and trade-offs without the full overhead of standard MADR or RFC-style templates.

How do you manage the review process for architecture decision records?

Manage architecture decision record reviews using guided review processes and automation guidance. This improves governance by ensuring decisions are properly evaluated before onboarding or implementation.

How do I document the deprecation of a previous architecture decision?

Document the deprecation of a previous architecture decision using the Deprecation ADR template. This records lifecycle events and tracks superseding decisions, maintaining historical traceability for future reference.