decision-records

Create, query, and update Architectural Decision Records with a standardized format.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/dhruvinrsoni/agentskills-garden --skill decision-records
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-records
Source: https://github.com/dhruvinrsoni/agentskills-garden/tree/main/skills/50-documentation/decision-records
Command: npx skills add https://github.com/dhruvinrsoni/agentskills-garden --skill decision-records

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of losing valuable design rationale by providing a structured way to record, manage, and retrieve Architectural Decision Records (ADRs).

Core Features & Use Cases

  • ADR Creation: Generate new ADRs following a standard context/decision/consequences format.
  • ADR Querying: Search and retrieve existing ADRs based on various criteria.
  • Lifecycle Management: Track the status and evolution of decisions over time.
  • Use Case: When your team decides to adopt a new database technology, use this skill to create an ADR documenting why that choice was made, what alternatives were considered, and the expected outcomes. Later, if a similar decision needs to be made, you can easily query past ADRs for historical context.

Quick Start

Create a new architectural decision record with the title "Use PostgreSQL for user data", the context "Need a scalable and reliable database for user profiles", and the decision "Adopt PostgreSQL due to its maturity and feature set".

Frequently Asked Questions about decision-records

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

FAQPage Schema
How do I document architectural decisions to preserve design rationale?

You track architectural decision lifecycles by updating ADR statuses from proposed to superseded. This maintains an ADR index and traces decision chains, ensuring design rationale evolution is captured and accessible.

What is the best way to track the lifecycle of an architectural decision?

You track architectural decision lifecycles by updating ADR statuses from proposed to superseded. This maintains an ADR index and traces decision chains, ensuring design rationale evolution is captured and accessible.

How do I query past ADRs for historical context on technical debt?

You create an ADR by providing a title, context, and decision. For example, title it "Use PostgreSQL for user data", add context about scalability needs, and state the decision to adopt PostgreSQL due to its feature set.

How do I create an ADR for a new database technology adoption?

You create an ADR by providing a title, context, and decision. For example, title it "Use PostgreSQL for user data", add context about scalability needs, and state the decision to adopt PostgreSQL due to its feature set.

Does ADR documentation work without external dependencies?

You query past ADRs by searching and retrieving existing architectural decision records based on specific criteria. This provides historical context on past technical debt and design choices to inform current decisions.