What problem does it solve? It prevents agents from escalating trivial implementation choices to users or making ad-hoc decisions that contradict project architecture, by enforcing a canonical decision precedence and clear escalation criteria. ## Core Features & Use Cases - Decision Precedence: Ranks canonical sources from project-wide policy down to local judgment, so conflicting guidance resolves deterministically. - Escalation Gating: Defines exactly when user confirmation is required, such as irreversible operations, merge authorization, external API contracts, or security risk acceptance. - Lifecycle Rules: Covers ADR supersession tracking, design-first workflows, dependency adoption checklists, naming responsibility, and early-stage compatibility policy. - Use Case: When an agent finds two conflicting conventions in a codebase, it checks ADRs and architecture docs first, follows the newer canonical source, and only asks the user if product semantics genuinely change. ## Quick Start Use the engineering-decisions skill to decide how to implement this change without asking me unnecessary questions.
