architecture-decision-records

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

Archives architectural decisions as ADR documents with context, alternatives, and rationale.

1|Updated Mar 31, 2026

Search Tags:#architecture #documentation #adr #traceability #software-design #decision-records #coding-sessions

Ready to run

npx skills add https://github.com/aayushsoam/clawbot-plus --skill architecture-decision-records-aayushsoam

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions tend to live in Slack threads, PR comments, or team memory, making it hard to trace why the codebase evolved a certain way. This skill captures those decisions as structured ADR documents that live alongside the code, preserving context, alternatives considered, and rationale.

Core Features & Use Cases

Auto-detect decision moments during coding sessions and prompt ADR creation.
Record ADRs with Context, Alternatives Considered, and Rationale, building a durable ADR log.
Keep ADRs in a consistent docs/adr structure with an index for easy navigation and future auditing.

Quick Start

Record this ADR when you want to capture an architectural decision.

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 during coding sessions?▼

Document architectural decisions during coding sessions by auto-detecting decision moments and generating structured ADR entries with context, alternatives considered, and rationale.

What is the best way to keep architectural decision records in a repository?▼

Keep architectural decision records in a consistent docs/adr directory structure with an index file, ensuring easy navigation and future auditing of your software design choices.

How do I replace scattered Slack notes with a traceable software design log?▼

Replace scattered Slack notes and threads by archiving architectural decisions as ADR documents that live alongside your code, preserving context and rationale for future auditing.

Do I need a specific framework to start writing ADR documents?▼

No specific framework is required to start writing ADR documents. The skill provides template guidance and a docs/adr structure to automatically generate entries without dependencies.

What should an architectural decision record include for future traceability?▼

An architectural decision record should include the context, alternatives considered, and rationale to build a durable ADR log that ensures future traceability of codebase evolution.

When should I create an ADR instead of just adding code comments?▼

Create an ADR instead of code comments when auto-detected decision moments occur during coding sessions, capturing broader context and alternatives that comments cannot adequately preserve.