architecture-decision-records

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.

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.

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.

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.

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.

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.