architecture-decision-records

Name: architecture-decision-records
Availability: InStock
Author: shirulot

Create and maintain Architecture Decision Records with structured templates.

Updated Jul 6, 2026

Search Tags:#architecture #documentation #adr #best-practices #decision-making #software-design

Ready to run

npx skills add https://github.com/shirulot/codex-skill --skill architecture-decision-records-shirulot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/shirulot/codex-skill/tree/main/architecture-decision-records
Command: npx skills add https://github.com/shirulot/codex-skill --skill architecture-decision-records-shirulot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of historical context and rationale behind technical choices, preventing knowledge loss and ensuring team alignment on architectural direction.

Core Features & Use Cases

Structured Documentation: Provides templates for standard, lightweight, and RFC-style ADRs to ensure consistency.
Lifecycle Management: Tracks the status of decisions from proposal to deprecation or supersession.
Use Case: When a team needs to decide between two database technologies, this skill provides the framework to document the trade-offs, drivers, and consequences, ensuring future developers understand why a specific path was chosen.

Quick Start

Use the architecture-decision-records skill to generate a new ADR template for the proposed microservices migration.

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 should I document technical decisions?▼

An Architecture Decision Record captures technical rationale and design trade-offs for software engineering teams. You should document technical decisions when evaluating technology stacks or architectural patterns to ensure historical auditability and team onboarding.

How do I create a standard ADR template for a microservices migration proposal?▼

To create an ADR template for microservices migration, use the skill to generate standard, lightweight, or RFC-style formats. This provides a structured framework to document trade-offs, drivers, and consequences for the proposed architectural change.

How do I track the lifecycle status of an Architecture Decision Record from proposal to deprecation?▼

Track ADR lifecycle status by managing decision records from initial proposal through to deprecation or supersession. This lifecycle management ensures historical auditability and maintains context for future developers evaluating architectural direction.

Can I use lightweight ADRs for smaller software design decisions instead of full RFC-style documentation?▼

Yes, you can use lightweight ADRs for smaller software design decisions. The skill provides multiple templates including standard, lightweight, and RFC-style formats to ensure consistency while matching the scale of your technical decision-making needs.

What's the best way to document database technology trade-offs for future developer onboarding?▼

The best way to document database technology trade-offs is using structured ADRs that capture drivers and consequences. This ensures future developers understand why a specific path was chosen, preventing knowledge loss and ensuring team alignment.

Why does my team lack historical context behind architectural choices and how do I prevent knowledge loss?▼

Teams lack historical context when technical choices are undocumented, causing knowledge loss. Prevent this by maintaining Architecture Decision Records that capture technical rationale and design trade-offs, ensuring team alignment on architectural direction.