architecture-decision-records

To document architecture decisions automatically, this Skill detects decision moments during Claude Code sessions and records context, alternatives, and rationale to generate structured ADR documents. It requires explicit confirmation before writing files.

Architecture decision records (ADRs) capture the context, alternatives, and rationale behind architectural decisions. You need them to maintain a log for codebase understanding and document the evolution of your software architecture.

To capture context and rationale for architectural decisions, activate the Skill and say "let's record this decision". It then detects the decision moment and records the context, alternatives, and rationale into a structured ADR document.

Yes, the architecture decision records Skill requires explicit confirmation before writing ADRs. It ensures explicit approval before creating directories and files to prevent unauthorized modifications to your codebase.

Yes, you can integrate architecture decision records with other workflows. The Skill integrates with other tools like the Planner agent and Code reviewer agent to provide a comprehensive workflow for capturing, reviewing, and updating ADRs.

The best way to maintain an ADR log for codebase understanding is to auto-detect decision moments during coding sessions and systematically record the context, alternatives, and rationale in structured ADR documents.