architecture-decision-records

Capture architectural decisions as structured ADR documents with context and rationale.

Updated Dec 22, 2025

Search Tags:#workflow #architecture #documentation #adr #rationale #decision-record

Ready to run

npx skills add https://github.com/senior-sigan/llm-skills --skill architecture-decision-records-senior-sigan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture architectural decisions as structured ADRs, ensuring rationale, context, and alternatives are preserved alongside code.

Core Features & Use Cases

Create ADR documents that capture context, decision, alternatives considered, and rationale.
Maintain a centralized ADR log (docs/adr) to help future developers understand why design choices were made.
Provide a repeatable workflow for capturing new ADRs and reading existing ones.

Quick Start

Ask to record a new ADR and follow the guided workflow to capture context, alternatives, and rationale, then save the ADR to docs/adr with an incremented number after your confirmation.

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 architecture decisions to preserve context and rationale alongside code?▼

To document architecture decisions, you capture structured ADRs that record context, alternatives considered, and rationale. This ensures design choices are preserved in a centralized log for future developers.

What is an architecture decision record and when do I need to create one?▼

An architecture decision record captures context and rationale for a design choice. You need to create an ADR when making technology choices, selecting architecture patterns, or deciding on deployment trade-offs.

How do I start capturing a new ADR for a technology choice during a coding session?▼

To start capturing a new ADR, request to record one and follow the guided workflow to capture context, alternatives, and rationale. It saves to docs/adr with an incremented number after your confirmation.

Can I use a standard ADR workflow to track deployment trade-offs across multiple projects?▼

Yes, you can apply a standard ADR workflow to track deployment trade-offs across projects. It provides a repeatable process for capturing new records and reading existing ones in a centralized log.

What is the best way to maintain a centralized log of architectural decisions for my team?▼

The best way to maintain a centralized log of architectural decisions is saving structured ADRs to a docs/adr directory. This provides a repeatable workflow for reading existing records and adding new ones.

Do I need a specific template to record alternatives and rationale in my decision logs?▼

You need a standard ADR template to record alternatives and rationale effectively. The workflow requires capturing context, decision, alternatives considered, and rationale to preserve design choices alongside your code.