architecture-decision-records

Name: architecture-decision-records
Availability: InStock
Author: Michae2xl

Capture architectural decisions and generate structured ADR documents.

1|Updated Apr 7, 2026

Search Tags:#ADR #codebase understanding #codebase documentation #architecture decision records #decision detection

Ready to run

npx skills add https://github.com/Michae2xl/claude-skills-michael --skill architecture-decision-records-michae2xl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/Michae2xl/claude-skills-michael/tree/main/skills/architecture-decision-records
Command: npx skills add https://github.com/Michae2xl/claude-skills-michael --skill architecture-decision-records-michae2xl

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill captures architectural decisions made during Claude Code sessions, ensuring they are documented as structured ADRs for future reference.

Core Features & Use Cases

Decision Detection: Automatically detects decision moments during coding sessions.
Context & Alternatives: Records context, alternatives considered, and rationale.
ADR Log: Maintains an ADR log for understanding the codebase's evolution.
Workflow: Provides a workflow for capturing, reviewing, and updating ADRs.
Integration: Integrates with other skills like Planner agent and Code reviewer agent.

Quick Start

Activate the skill and say "let's record this decision" when you make an architectural decision during a coding session.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema

How do I document architecture decisions automatically during coding sessions?▼

To document architecture decisions automatically, this Skill detects decision moments during Claude Code sessions and records context, alternatives, and rationale to generate structured ADR documents. It requires explicit confirmation before writing files.

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

Architecture decision records (ADRs) capture the context, alternatives, and rationale behind architectural decisions. You need them to maintain a log for codebase understanding and document the evolution of your software architecture.

How to capture context and rationale when making architectural decisions in Claude Code?▼

To capture context and rationale for architectural decisions, activate the Skill and say "let's record this decision". It then detects the decision moment and records the context, alternatives, and rationale into a structured ADR document.

Does this architecture decision records Skill require manual confirmation to write files?▼

Yes, the architecture decision records Skill requires explicit confirmation before writing ADRs. It ensures explicit approval before creating directories and files to prevent unauthorized modifications to your codebase.

Can I integrate architecture decision records with other codebase documentation workflows?▼

Yes, you can integrate architecture decision records with other workflows. The Skill integrates with other tools like the Planner agent and Code reviewer agent to provide a comprehensive workflow for capturing, reviewing, and updating ADRs.

What is the best way to maintain an ADR log for codebase understanding?▼

The best way to maintain an ADR log for codebase understanding is to auto-detect decision moments during coding sessions and systematically record the context, alternatives, and rationale in structured ADR documents.