adr

Name: adr
Availability: InStock
Author: Roxabi

Create and list Architecture Decision Records with automated numbering and markdown generation.

9|1|Updated Feb 28, 2026

Search Tags:#architecture #decision making #documentation #knowledge management #adr #technical debt

Ready to run

npx skills add https://github.com/Roxabi/roxabi-plugins --skill adr-roxabi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/Roxabi/roxabi-plugins/tree/main/plugins/dev-core/skills/adr
Command: npx skills add https://github.com/Roxabi/roxabi-plugins --skill adr-roxabi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of creating and managing Architecture Decision Records (ADRs), ensuring that the reasoning behind technical choices is clearly documented and easily accessible.

Core Features & Use Cases

ADR Creation: Guides users through documenting context, options considered, the final decision, and consequences.
Automated Numbering: Automatically determines the next sequential number for new ADRs.
Metadata Management: Updates a central meta.json file for easy referencing and listing.
List ADRs: Provides a formatted table of existing ADRs with their status and date.
Use Case: When your team decides to switch from one database to another, use this skill to document the reasons, alternatives considered, and the final choice, creating a permanent record for future reference.

Quick Start

Use the adr skill to create a new architecture decision record for "Using Bun as the runtime".

Frequently Asked Questions about adr

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

FAQPage Schema

What is an architecture decision record and when should I document one?▼

An architecture decision record (ADR) documents the context, options considered, final decision, and consequences of a technical choice. You should create an ADR whenever your team makes a significant technical decision to maintain clear knowledge management and mitigate technical debt.

How do I create a new architecture decision record using an interview-style format?▼

To create an architecture decision record, the Skill guides you through interview-style questions to gather context, alternatives, and consequences, then automatically generates a structured markdown file with sequential numbering and updates a central meta.json file for tracking.

Can I view a list of existing architecture decision records in a formatted table?▼

Yes, you can list existing architecture decision records to view a formatted table displaying each record's status and date, pulling metadata from the central meta.json file to provide a comprehensive overview of your technical decisions.

Does this ADR tool automatically handle sequential numbering for new technical decisions?▼

Yes, the ADR tool automatically determines the next sequential number for new architecture decision records, ensuring consistent ordering and preventing numbering conflicts when documenting technical choices across your software engineering projects.

What is the best way to document technical decisions to reduce knowledge loss and technical debt?▼

The best way to document technical decisions is using structured architecture decision records that capture context, options, and consequences in markdown files with centralized metadata tracking, ensuring reasoning remains accessible and reducing future technical debt.

Are there limitations to managing architecture decision records with markdown and meta.json files?▼

Managing architecture decision records via markdown files and a meta.json file provides lightweight, version-controllable documentation, but may lack advanced search or collaboration features found in dedicated knowledge management platforms for larger engineering teams.