What problem does it solve? Teams often struggle to decide which technical changes deserve a formal Architecture Decision Record and which should be handled as ordinary requirement or design updates, leading to either decision-record sprawl or missed documentation of critical choices. ## Core Features & Use Cases - Decision Threshold Evaluation: Applies criteria such as architectural significance, long-term impact, and reversibility cost to judge whether a change warrants a Decision record. - Boundary Rules: Distinguishes Decision-worthy topics from specification changes, workflow definitions, naming conventions, and template updates that belong in REQ/Design/guide documents. - Lifecycle Guidance: Defines Proposed, Accepted, Superseded, and Deprecated states plus rules for immutability and non-semantic corrections of accepted Decisions. - Use Case: When proposing to adopt a new authentication scheme or change a data access pattern, use this Skill to determine whether to draft a new Decision, update an existing one, or handle it as a Design document change. ## Quick Start Ask the agent to evaluate whether your proposed architecture change, such as switching the data access layer to the Repository pattern, requires creating a new Decision record.
