skills.rest
arbisoft
arbisoftOFFICIAL
Explore all skills by this author →
Website𝕏@arbisoftGitHub

architecture-decision-records

Generate structured ADR documents with context, decision, alternatives, and consequences.

4|7|Updated Apr 9, 2026
Search Tags:#workflow#architecture#documentation#adr#traceability#decision-records
One-click install
npx skills add https://github.com/arbisoft/ai-skillforge --skill architecture-decision-records-arbisoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/arbisoft/ai-skillforge/tree/main/Claude/skills/architecture-decision-records
Command: npx skills add https://github.com/arbisoft/ai-skillforge --skill architecture-decision-records-arbisoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This ADR tool helps capture architectural decisions in real-time during Claude Code sessions, ensuring decisions, context, alternatives, and rationales are preserved alongside the codebase.

Core Features & Use Cases

  • Automated ADR generation: ADR documents following the standard format, with sections for context, decision, alternatives, consequences, and risks.
  • ADR workflow and lifecycle: Detect decision moments, guide capture, maintain an index, and support reading existing ADRs.
  • Readable traceability: Keeps an ADR log that helps future developers understand why the codebase is shaped this way and how decisions evolved.

Quick Start

Record an ADR for the current architectural decision by saying ADR this.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema
How do I capture architectural decisions during a coding session?▼

Capturing architectural decisions during a coding session involves generating structured ADR documents automatically. This records the context, alternatives, and consequences of your technology choices in real-time alongside the codebase.

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

An architecture decision record (ADR) is a structured document that captures the context, decision, alternatives, and consequences of a software architectural choice. You need one for feature design, technology choices, and trade-offs to ensure traceability.

How do I document architectural trade-offs and alternatives?▼

Documenting architectural trade-offs and alternatives requires using a consistent ADR format. This format mandates sections for context, decision, alternatives, consequences, and risks, providing an auditable log for future developers.

Can I generate an ADR document during a live design review?▼

Yes, you can generate an ADR document during a live design review. The tool detects decision moments across planning, live coding, and design reviews, guiding the capture of architectural choices as they occur.

What is the best way to maintain an auditable log of technology choices?▼

The best way to maintain an auditable log of technology choices is to maintain an accessible ADR index. This ensures readable traceability, helping future developers understand how and why the codebase architecture evolved.

Related Skills

Explore More Software Engineering Skills→
CyapstayeCyapstaye
9

llm-wiki

Ingests raw sources and synthesizes them into structured, interlinked entity and page documents.

Community
Advanced
dhar174dhar174
1

mermaid-diagrams

Generate flowcharts, sequence, class, ER, and Gantt diagrams from Mermaid syntax.

Community
Intermediate
c-tomiokac-tomioka

adr-madr

Generate MADR-compliant architectural decision records from git logs, pull requests, or freeform text.

Community
Intermediate
farzanmrzfarzanmrz
6

documentation-and-adrs

Record architecture decisions and rationale in structured ADR templates.

Community
Intermediate