skills.rest
iDako7
iDako7COMMUNITY
Explore all skills by this author →
GitHub

architecture-decision-records

Capture architectural decisions as structured ADR documents during coding and design sessions.

1|Updated Apr 6, 2026
Search Tags:#architecture#documentation#adr#code-review#design-decisions#decision-records
One-click install
npx skills add https://github.com/iDako7/Smart_Grocery_Agent --skill architecture-decision-records-idako7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/iDako7/Smart_Grocery_Agent/tree/main/.claude/skills/architecture-decision-records
Command: npx skills add https://github.com/iDako7/Smart_Grocery_Agent --skill architecture-decision-records-idako7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and preserve architectural decisions that would otherwise be lost in chat history or pull request comments by producing structured ADR documents that live alongside the codebase.

Core Features & Use Cases

  • Decision capture: Detects explicit and implicit decision signals and prompts to record an ADR when a meaningful architectural choice occurs.
  • Structured ADR authoring: Produces ADRs with Decision, Context, Why, Alternatives considered, and Risk, and recommends the appropriate document location and sequential numbering.
  • Discovery and review: Reads existing ADRs to explain past choices, flags conflicts or superseded decisions, and integrates with architect, planner, and code-review workflows.
  • Use case: During a framework or database selection discussion, draft ADR-8 with rationale and rejected alternatives and present it for user approval before saving.

Quick Start

Record a new ADR describing the decision to use PostgreSQL instead of SQLite, include context, alternatives considered, rationale, and suggested file location.

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?▼

Document architectural decisions by capturing decision context, rationale, alternatives, and risks as structured Architecture Decision Records inline within project architecture docs or a dedicated docs/adr/ directory.

What is an ADR and when should I create one?▼

An ADR is a structured Architecture Decision Record that captures context, decisions, and rationale. Create an ADR during planning phases, architecture discussions, code reviews, or tool and database selection scenarios.

How do I generate an ADR for a database selection like PostgreSQL versus SQLite?▼

Generate an ADR by recording the decision, context, rationale, rejected alternatives, and risks. The ADR is then assigned sequential numbering and a suggested file location before presentation for user approval.

Can I detect conflicts between new design decisions and existing architecture documentation?▼

Conflict detection is supported by reading existing ADRs to explain past choices, flagging conflicts, and identifying superseded decisions before persisting new architectural records.

Does this approach require a specific framework or external dependencies?▼

No external dependencies are required. ADRs are stored directly within the project codebase architecture docs or docs/adr/ directory, integrating seamlessly into existing architect, planner, and code-review workflows.

What is the best way to track superseded architectural decisions during code review?▼

Track superseded decisions by reading existing ADRs to explain past choices and flag conflicts before persisting. Sequential numbering ensures traceability of decisions, alternatives, and rationale throughout the project lifecycle.

Related Skills

Explore More Software Engineering Skills→
VitaDynamicsVitaDynamics

adr

Create sequentially numbered Architecture Decision Records in docs/adr/.

Official
Intermediate
cescraflicescrafli

architecture-decision-records

Capture architectural decisions as structured ADR documents with context and alternatives.

Community
Advanced
riftzen-bitriftzen-bit

architecture-decision-records

Capture architectural decisions as structured ADR documents during design discussions and coding sessions.

Community
Intermediate
jayteealaojayteealao

diataxis:explanation

Document architectural rationale, context, and trade-offs for subsystem decisions.

Community
Intermediate