architecture-decision-records

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

Capture architectural decisions as structured ADR documents under docs/adr.

Updated Aug 23, 2026

Search Tags:#workflow #architecture #documentation #adr #engineering #decision-record #coding-session

Ready to run

npx skills add https://github.com/contentbugvideoediting/cb-project-assistant --skill architecture-decision-records-contentbugvideoediting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/contentbugvideoediting/cb-project-assistant/tree/main/services/cb-s-claude/vendor/s-claude/skills-library/architecture-decision-records
Command: npx skills add https://github.com/contentbugvideoediting/cb-project-assistant --skill architecture-decision-records-contentbugvideoediting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture architectural decisions as they happen during Claude Code sessions and record them as ADRs so future developers understand the rationale.

Core Features & Use Cases

Structured ADRs: Generate ADR documents that capture context, alternatives, decision, and consequences.
Incremental ADRs: Auto-increment ADR numbers and maintain an ADR log alongside code.
Context-aware prompts: Trigger ADR capture during coding sessions, planning, or reviews with explicit user confirmation.

Quick Start

Record a new ADR for the latest architectural decision in the codebase with context.

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 made during a coding session?▼

You capture architectural decisions by triggering this skill during a Claude Code session, which records the context, alternatives, and rationale into a structured ADR document under the docs/adr directory.

What is an Architecture Decision Record and when should I create one?▼

An Architecture Decision Record (ADR) is a structured document that captures the context, alternatives, decision, and consequences of a software engineering choice. You should create one during design reviews or planning moments to preserve rationale for future developers.

How do I maintain an ADR log and index as new architecture decisions are made?▼

To maintain an ADR log, this skill auto-increments the ADR number for each new document and automatically updates the ADR index, ensuring the architecture decision record log stays synchronized with the codebase alongside your code.

Can I review and confirm architectural documentation before it is written to the repository?▼

Yes, you can review architectural documentation before it is saved. The skill requires explicit user confirmation before creating any ADR files in the docs/adr directory, ensuring you control exactly what context and rationale gets recorded.

Does this ADR workflow require any external dependencies or specific file components?▼

No, this ADR workflow requires no external dependencies or specific file components to function. It operates natively within Claude Code sessions to generate architecture decision records directly in your repository.

What is the best way to capture engineering rationale alongside code changes?▼

The best way to capture engineering rationale alongside code changes is to trigger ADR capture during coding sessions. This records the decision context and alternatives incrementally in a structured format under docs/adr, keeping documentation aligned with development.