What problem does it solve? Teams lose shared understanding as projects grow: terms drift, decisions get forgotten, and code contradicts what stakeholders say. This Skill keeps the project's domain model sharp by capturing vocabulary and decisions the moment they crystallise during design conversations. ## Core Features & Use Cases - Glossary Maintenance: Challenges conflicting or fuzzy terminology and updates docs/GLOSSARY.md inline, moving replaced terms to a Deprecated table instead of deleting them. - Decision Recording: Applies a three-part test (hard to reverse, surprising without context, real trade-off) to decide when a decision deserves an ADR, then scaffolds it with /document adr. - Code Cross-Referencing: Checks whether stated domain behavior matches the actual code and surfaces contradictions. - Use Case: During a feature discussion, a user says "cancel the account." The Skill flags that the glossary distinguishes Customer from User, proposes a precise term, updates the glossary row, and offers an ADR when the cancellation policy decision settles. ## Quick Start Ask the assistant to help pin down the domain terminology for a new feature and record any architectural decisions that come out of the discussion.
