architecture-decision-records

Create structured architecture decision records in markdown files.

Updated Mar 15, 2026

Search Tags:#architecture #software design #decision record #ADR #system architecture

Ready to run

npx skills add https://github.com/abhishekdutta18/blogspro --skill architecture-decision-records-abhishekdutta18

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables systematic recording of architectural decisions to ensure clarity and knowledge sharing within development teams.

Core Features & Use Cases

Decision Capture: Automatically detect decision-making moments during development sessions or discussions.
ADR Management: Create, document, and organize architecture decision records following best practices.
Use Case: During system planning, record the choice of database technology or deployment strategy with detailed rationale and alternatives considered, accessible later for reference.

Quick Start

Ask the AI to create a new ADR for a proposed microservices architecture or review existing ADRs to understand past decisions.

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 architectural decisions for my software project?▼

You document architectural decisions by creating structured Architecture Decision Records (ADRs) as markdown files within the docs/adr/ directory to capture context, alternatives, and consequences for your engineering team.

What is the best way to track system architecture choices during development?▼

Tracking system architecture choices is best handled by using ADRs to record the decision-making moments, ensuring a formal, structured history of your software design rationale that is accessible for later reference.

Can I automatically capture architecture decision records during planning sessions?▼

Yes, you can automatically detect decision-making moments during development sessions or discussions to systematically create and organize ADRs without interrupting your system planning workflow.

Do I need a specific framework to manage architecture decision records?▼

You do not need a specific framework to manage architecture decision records, as the process relies on creating and organizing standard markdown files within your project's docs/adr/ directory.

How do I record the alternatives considered when choosing a database technology?▼

You record database technology alternatives by documenting the detailed rationale within an ADR, capturing the specific context, alternatives evaluated, and consequences of your chosen deployment strategy or architecture.