architecture-decision-records

Create and manage structured Architecture Decision Records with templates and lifecycle tracking.

Updated May 25, 2026

Search Tags:#software architecture #ADR #project documentation #document management #architecture decision records

Ready to run

npx skills add https://github.com/ngquaanghuy/Crypto --skill architecture-decision-records-ngquaanghuy

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you create, maintain, and manage Architecture Decision Records (ADRs) efficiently, ensuring that significant technical decisions are well-documented and easily accessible.

Core Features & Use Cases

Create and manage ADRs: Automatically draft, structure, and categorize ADRs based on your team's best practices.
Lifecycle management: Track the status of ADRs from proposal to implementation, deprecated, or superseded.
templates and guides: Access standardized templates for various ADR types to ensure consistency and clarity.
Documentation and references: Keep your decision history, motivations, and trade-offs at your fingertips.

Quick Start

To get started with this Skill, open your technical documentation repository and activate it by calling 'skill activate architecture-decision-records'.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema

How do I create and manage architecture decision records for my software project?▼

To create architecture decision records, you draft and structure ADRs using standardized templates within your technical documentation repository. This ensures significant technical decisions are well-documented, categorized, and easily accessible for your team.

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

Tracking an architecture decision record involves monitoring its status from proposal through implementation to deprecated or superseded. This lifecycle management maintains traceability and consistency for critical project decisions over time.

Does this architecture decision record tool require any specific dependencies or frameworks?▼

No dependencies are required to manage architecture decision records. You simply open your technical documentation repository and activate the workflow to begin drafting and categorizing your project's architectural decisions.

Why do I need standardized templates for documenting architectural decisions?▼

Standardized templates for architecture decision records ensure consistency and clarity across your project documentation. They provide structured guides for various ADR types, capturing decision history, motivations, and trade-offs effectively.

Can I maintain decision history and trade-offs for technical projects automatically?▼

Yes, you can maintain decision history and trade-offs for technical projects by employing structured workflows and review processes. This keeps your architectural decision records accessible and traceable at your fingertips.