architectural-decision-records

Name: architectural-decision-records
Availability: InStock
Author: Agentient

Automate architectural decision documentation with standard ADR templates and lifecycle statuses.

2|1|Updated Jan 31, 2026

Search Tags:#architecture #templates #documentation #adr #governance #decision-records #design-tradeoffs

Ready to run

npx skills add https://github.com/Agentient/vibekit --skill architectural-decision-records

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architectural-decision-records
Source: https://github.com/Agentient/vibekit/tree/main/plugins/frontend-tools/skills/architectural-decision-records
Command: npx skills add https://github.com/Agentient/vibekit --skill architectural-decision-records

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture Decision Records (ADRs) provide a formal mechanism to capture the rationale behind significant technical decisions, not just the decisions themselves, enabling future traceability and accountability.

Core Features & Use Cases

Standard ADR templates and guidance to structure decisions.
Lifecycle governance and templates for Proposed, Accepted, Deprecated, and Superseded statuses.
Scenarios include technology selections, architectural patterns, performance trade-offs, and data modeling decisions across projects.
Use case: create ADRs to document why a particular framework or design approach was chosen.

Quick Start

Create a new ADR following the ADR template and store it under docs/adr with the next sequential ADR number.

Frequently Asked Questions about architectural-decision-records

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are Architecture Decision Records used for in software engineering?▼

Architecture Decision Records are used to formally capture the rationale behind significant technical decisions, enabling future traceability and accountability for technology choices and design trade-offs across projects.

How do I document architectural decisions and design trade-offs?▼

You document architectural decisions by applying a standard ADR template to structure the decision, storing the file under docs/adr with the next sequential ADR number for organized lifecycle governance.

When should I create an ADR for my project?▼

You should create an ADR for scenarios like technology selections, architectural patterns, performance trade-offs, and data modeling decisions to ensure the design rationale is recorded for future reference.

How do I manage the lifecycle status of an Architecture Decision Record?▼

You manage an Architecture Decision Record by applying lifecycle statuses, moving records through Proposed, Accepted, Deprecated, and Superseded states to maintain governance and track decision history.

What is the best way to structure technology selection documentation?▼

The best way to structure technology selection documentation is using a standard ADR template that systematically records the chosen framework and the specific rationale behind the design approach.

Do I need any specific dependencies to start documenting decision rationales?▼

No dependencies are required to start documenting decision rationales; you only need to create a file following the ADR template and store it under the docs/adr directory with sequential numbering.