architecture-decision-records

Create and manage Architecture Decision Records with lifecycle tracking.

Updated Aug 23, 2026

Search Tags:#architecture #decision making #documentation #adr #rfc #technical decisions

Ready to run

npx skills add https://github.com/ACGSpgp/ACGS --skill architecture-decision-records-acgspgp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/ACGSpgp/ACGS/tree/main/.agent/workflows/documentation-generation/1.2.0/skills/architecture-decision-records
Command: npx skills add https://github.com/ACGSpgp/ACGS --skill architecture-decision-records-acgspgp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires adr-tools, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured approach to documenting significant technical decisions, ensuring clarity, rationale, and historical context for architectural choices.

Core Features & Use Cases

ADR Creation: Generate new Architecture Decision Records using various templates (Standard, Lightweight, Y-Statement, Deprecation, RFC).
ADR Management: Organize ADRs within a defined directory structure and maintain an index.
Lifecycle Tracking: Manage the status of ADRs (Proposed, Accepted, Deprecated, Superseded, Rejected).
Use Case: When deciding to adopt a new framework, choose a database technology, or change an API design pattern, use this Skill to create a formal ADR that captures the context, decision, and consequences.

Quick Start

Use the architecture-decision-records skill to create a new ADR titled "Adopt TypeScript for Frontend Development".

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema

How do I document technical decisions for my software architecture?▼

To document technical decisions, you create Architecture Decision Records (ADRs) that capture the context, decision, and consequences of architectural choices for historical reference.

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

The best way to track an architecture decision lifecycle is by managing ADR statuses, moving records through Proposed, Accepted, Deprecated, Superseded, or Rejected phases.

Can I use different formats for architecture decision records?▼

Yes, you can use multiple ADR formats including Standard, Lightweight, Y-Statement, Deprecation, and RFC styles to document technical decisions based on your needs.

How do I organize ADRs within my project repository?▼

You organize ADRs by placing them within a defined directory structure and maintaining an index to ensure architectural decisions are tracked and accessible.

Do I need adr-tools to manage architecture decision records?▼

Yes, this Skill requires adr-tools as a dependency to facilitate the creation and management of Architecture Decision Records and maintain organizational best practices.

When should I use an RFC style ADR instead of a standard template?▼

You use an RFC style ADR when you need a formal review process for significant technical decisions, whereas standard templates suffice for simpler architectural choices.