skills.rest
zero3041
zero3041COMMUNITY
Explore all skills by this author →
GitHub

architecture-decision-records

Detect decision-making moments and extract architectural decision records.

1|Updated Apr 6, 2026
Search Tags:#ADR#codebase understanding#decision documentation#developer collaboration#architecture decision records
One-click install
npx skills add https://github.com/zero3041/PREP --skill architecture-decision-records-zero3041
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/zero3041/PREP/tree/main/.claude/skills/skills/architecture-decision-records
Command: npx skills add https://github.com/zero3041/PREP --skill architecture-decision-records-zero3041

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automatically captures architectural decisions during code sessions and maintains them in a structured ADR format, improving codebase understanding and decision traceability.

Core Features & Use Cases

  • Automated ADR Creation: Detects decision moments and captures context, alternatives, and rationale.
  • ADR Log Maintenance: Maintains an organized ADR log for easy reference.
  • Use Case: Use the skill to record decisions like choosing a framework, database, or architecture pattern, ensuring all decisions are documented and traceable.

Quick Start

When making an architectural decision, say "let's record this decision" or "ADR this" to initiate the ADR creation process.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema
How do I automate architecture decision records creation during development?▼

Automate architecture decision records creation by detecting decision-making moments in natural language and extracting context, alternatives, and rationale to maintain traceable technical decision history.

When do I need architecture decision records for codebase understanding?▼

Architecture decision records are needed when choosing frameworks, databases, or architecture patterns, ensuring all technical decisions are documented, traceable, and accessible for team reference.

How do I maintain an ADR log for developer collaboration?▼

Maintain an ADR log by automatically indexing captured architectural decisions, creating an organized repository of technical decision-making history for easy team reference and codebase understanding.

Does automated ADR documentation capture decision rationale and alternatives?▼

Automated ADR documentation captures decision rationale and alternatives by utilizing natural language processing to extract relevant information from decision-making moments during code development sessions.

Related Skills

Explore More Software Engineering Skills→
KanakMalpaniKanakMalpani

architecture-decision-records

Document architectural decisions in ADR format with Context, Decision, Alternatives, and Consequences.

Community
Advanced
betaTridentbetaTrident

architecture-decision-records

Capture and maintain structured architectural decision records using a standard ADR template.

Community
Intermediate
nesihaver-ILnesihaver-IL

update-docs

Update README, API, architecture docs, and changelogs after code changes.

Community
Intermediate
zrosenfieldzrosenfield
84

decision-log

Extract structured Decision Records from video or audio transcripts.

Community
Intermediate