Architecture Decision Records Manager FAQs

Question 1

Can I use this skill with existing adr-tools?

Accepted Answer

Yes, the skill is designed to work alongside common CLI tools like adr-tools to initialize directories, link related decisions, and generate tables of contents.

Question 2

Which ADR templates are supported by this skill?

Accepted Answer

The skill supports multiple formats including Markdown Architecture Decision Records (MADR), Lightweight ADRs, Y-Statements, and RFC (Request for Comments) styles.

Question 3

What is an Architecture Decision Record (ADR)?

Accepted Answer

An ADR is a short text file that captures a significant architectural decision, including the context in which it was made, the options considered, and the resulting consequences.

Question 4

How does this improve team collaboration?

Accepted Answer

It creates a shared 'source of truth' for technical decisions, reducing repetitive arguments and helping new team members understand why the system is built the way it is.

Question 5

When should I write an ADR instead of a regular document?

Accepted Answer

You should write an ADR for significant, hard-to-reverse choices like new framework adoption or database changes. Minor implementation details or bug fixes do not require an ADR.

Architecture Decision Records Manager

Key Features

Use Cases

Architecture Decision Records Manager

Key Features

Use Cases