doc-adr

Create Architecture Decision Records with rationale, alternatives, and consequences.

16|3|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-adr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-adr
Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-adr
Command: npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates Architecture Decision Records (ADR) that document architectural decisions with rationale, alternatives, and consequences to guide future work.

Core Features & Use Cases

  • Capture decision context, choice, and rationale
  • List alternatives and consequences
  • Tie ADR to BRD/PRD/EARS/BDDs for traceability

Quick Start

Create an ADR that captures a decision, its rationale, and the consequences for system evolution.

Frequently Asked Questions about doc-adr

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

FAQPage Schema
How do I document architectural decisions with rationale and consequences?▼

Architecture Decision Records (ADRs) document architectural decisions by capturing the decision context, alternatives considered, and consequences. ADRs create a traceable history of why specific architectural choices were made, guiding future development and preventing revisiting settled decisions.

What should be included in an Architecture Decision Record?▼

An ADR captures decision context, the chosen option, rationale for the choice, alternatives that were rejected, and long-term consequences for system evolution. The four-part template ensures consistency and links decisions to upstream artifacts like BRD, PRD, EARS, and BDD documents.

How do I trace architectural decisions back to requirements?▼

ADRs include traceability tags and references to upstream BRD, PRD, EARS, and BDD artifacts, establishing a chain from business requirements through architectural choices to implementation. This creates accountability and enables impact analysis when requirements change.

Can I use diagrams in Architecture Decision Records?▼

Yes, ADRs support Mermaid diagrams to visualize architectural options and their consequences, making decision context clearer and more accessible to team members reviewing the record.

When should I create an Architecture Decision Record?▼

Create ADRs for significant architectural decisions during Layer 5 system design workflow, particularly when evaluating alternatives with long-term impact. ADRs ensure decisions are documented before implementation and capture the reasoning while it's fresh.

How do Architecture Decision Records support system readiness?▼

ADRs contribute to SYS-Ready scoring by providing documented rationale, alternatives analysis, and consequence evaluation for architectural choices, demonstrating that decisions were made systematically and defensibly.