arch-decision-records

Document architectural decisions with structured templates for context, rationale, and consequences.

3|Updated Jan 25, 2026

Search Tags:#architecture #documentation #adr #traceability #rationale #software-design #decision-records

Ready to run

npx skills add https://github.com/ai-enhanced-engineer/aiee-team --skill arch-decision-records

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: arch-decision-records
Source: https://github.com/ai-enhanced-engineer/aiee-team/tree/main/skills/arch-decision-records
Command: npx skills add https://github.com/ai-enhanced-engineer/aiee-team --skill arch-decision-records

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADRs capture the rationale behind architectural choices to preserve decision history and avoid repeated debates.

Core Features & Use Cases

Structured ADR templates for Context, Decision, Consequences, and References
One decision per ADR to keep decisions focused and traceable
Lifecycle guidance from Proposed to Superseded for historical accuracy

Quick Start

Create your first ADR (e.g., ADR-001) documenting context, decision, and consequences.

Frequently Asked Questions about arch-decision-records

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

FAQPage Schema

What are architecture decision records and when do I need them?▼

An architecture decision record (ADR) documents architecturally significant decisions with rationale and traceable context. You need ADRs in software architecture projects to record technology choices, constraints, and rationale for future reference.

How do I document architectural decisions with rationale and traceable context?▼

You document architectural decisions using structured ADR templates with sections for Context, Decision, Consequences, and References. Each ADR captures one decision per record to keep decisions focused and traceable for future reference.

How do I track the lifecycle status of an architecture decision record?▼

You track the lifecycle status of an architecture decision record using lifecycle guidance from Proposed to Superseded. This ensures historical accuracy by maintaining a clear record of how decisions evolve over time.

What's the best way to structure an ADR template for software design choices?▼

The best way to structure an ADR template is using sections for Context, Decision, Consequences, and References. Keeping one decision per ADR ensures decisions remain focused and traceable for future reference in software architecture projects.

Can I use ADRs to record technology choices and constraints for future reference?▼

Yes, you can use ADRs to record technology choices and constraints for future reference. ADRs capture the rationale behind architectural choices to preserve decision history and avoid repeated debates in software architecture projects.

Why does my team keep debating the same architectural decisions repeatedly?▼

Your team keeps debating because the rationale behind architectural choices is not being preserved. Architecture decision records solve this by capturing decision history, ensuring technology choices and constraints are documented with traceable context for future reference.