architecture-decision-records

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

Updated Mar 20, 2026

Search Tags:#workflow #architecture #documentation #codebase #adr #traceability #decision-recording

Ready to run

npx skills add https://github.com/KanakMalpani/General-Private-Skills --skill architecture-decision-records-kanakmalpani

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/KanakMalpani/General-Private-Skills/tree/main/skills/architecture-decision-records
Command: npx skills add https://github.com/KanakMalpani/General-Private-Skills --skill architecture-decision-records-kanakmalpani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADRs help teams avoid losing critical architectural choices in scattered chats or PR discussions by turning decisions into structured, codified documents that live with the codebase. By capturing the context, alternatives considered, and rationale, new contributors understand why a path was chosen and how to proceed.

Core Features & Use Cases

Auto-detect decision moments during coding sessions and prompt to create a new ADR
Record Context, Decision, Alternatives Considered, and Consequences in a standardized ADR format
Maintain an ADR log with a canonical index (docs/adr) and automatic numbering to ensure traceability across the project

Quick Start

Record the current architectural decision as an ADR by providing the title, context, alternatives, and rationale.

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 in my codebase?▼

You document architectural decisions by creating ADRs that capture Context, Decision, Alternatives, and Consequences. This skill structures those records and maintains an indexed log in docs/adr to ensure traceability across your project.

What is the ADR format for recording software design choices?▼

The ADR format for recording design choices consists of Context, Decision, Alternatives Considered, and Consequences. This standardized structure codifies why a path was chosen so new contributors understand the rationale.

How do I maintain an ADR index for project traceability?▼

You maintain ADR traceability by keeping a canonical index in docs/adr with automatic numbering. The skill updates this log whenever a new architectural decision is recorded, ensuring continuous project history.

Can I capture decision moments automatically during coding sessions?▼

Yes, you can capture decision moments automatically. The skill auto-detects architectural decision points during coding sessions and prompts you to create a new ADR to prevent losing critical choices in scattered chats.

Why should I use ADRs instead of tracking decisions in PR discussions?▼

You should use ADRs because PR discussions and chats scatter critical architectural choices, making them hard to find. ADRs turn decisions into structured, codified documents that live permanently with your codebase.

Do I need any specific dependencies to create architecture decision records?▼

No specific dependencies are required to create architecture decision records. The skill operates independently to generate standardized ADR files and manage the index within your existing documentation structure.