architecture-decision-records

Create and manage architecture decision records with multiple format templates.

Updated Feb 26, 2026

Search Tags:#architecture #decision making #documentation #software design #adr #technical debt

Ready to run

npx skills add https://github.com/TheGreatL/KanbanBoard --skill architecture-decision-records-thegreatl

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured framework for documenting significant technical decisions, ensuring clarity, consistency, and maintainability of architectural choices over time.

Core Features & Use Cases

ADR Creation: Generate new Architecture Decision Records using various templates (Standard, Lightweight, Y-Statement, Deprecation, RFC).
ADR Management: Organize, track, and update the status of ADRs (Proposed, Accepted, Deprecated, Superseded, Rejected).
Use Case: When deciding on a new database technology, use this Skill to create an ADR that captures the context, decision drivers, considered options, the final decision, and its consequences, providing a clear record for future reference.

Quick Start

Use the architecture-decision-records skill to create a new ADR for adopting TypeScript.

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 software architecture decisions for my project?▼

Architecture Decision Records document significant technical decisions by capturing context, decision drivers, considered options, the final decision, and consequences. This skill provides structured templates to ensure clarity and maintainability of architectural choices over time.

What ADR formats can I use for technical decision documentation?▼

You can use multiple ADR formats including MADR, lightweight, Y-statement, deprecation, and RFC styles. Each template serves different documentation needs, from quick captures to comprehensive architectural proposals.

How do I manage the lifecycle of an Architecture Decision Record?▼

ADR lifecycle management involves organizing, tracking, and updating record statuses such as Proposed, Accepted, Deprecated, Superseded, or Rejected. This ensures technical decisions remain accurate and traceable as your software evolves.

Do I need adr-tools to automate Architecture Decision Record creation?▼

Yes, this skill integrates with the adr-tools dependency to automate ADR creation and management. The integration provides templates and scripting support for structured technical documentation.

When should I create an Architecture Decision Record?▼

Create an ADR when making significant technical decisions, such as adopting a new database technology or framework. Documenting the context, options, and consequences provides a clear record for future reference and helps manage technical debt.

What's the best way to structure an ADR for adopting a new technology?▼

Use a structured template to capture context, decision drivers, considered options, the final decision, and its consequences. This skill offers standard, MADR, and Y-statement formats to ensure your technical decisions are thoroughly documented.