record-decision

To create an Architectural Decision Record, you record the significant architectural choice, its rationale, and alternatives considered. The skill generates an ADR and automatically updates relevant adoption files like architecture.md to reflect the new project state.

Documenting non-architectural decisions like library choices uses Decision Log Entries (ADLs). The skill records these decisions and updates corresponding adoption files such as tech-stack.md, ensuring your project documentation remains a single source of truth.

Yes, you can update existing decision logs. The skill manages the decision lifecycle by detecting existing records, allowing for updates or new entries, and ensuring consistency between the original decision rationale and the current project state.

ADRs and ADLs maintain documentation consistency by automatically updating relevant adoption files. When a decision is recorded, the skill modifies files like tech-stack.md or architecture.md to accurately reflect the adopted changes and maintain an audit trail.

Use an ADL for non-architectural decisions such as convention adoptions or library choices, while ADRs are for significant architectural choices. Both generate records that systematically document project evolution and update adoption files.