What problem does it solve? Cross-team confusion is usually vocabulary confusion: PM says "account," engineering hears "user," and an entire spec gets built on a word two people read differently. This Skill keeps one shared, living definition of every load-bearing term as a knowledge entry in .hero/knowledge, so specs reference a single canonical meaning instead of silently re-defining terms. ## Core Features & Use Cases - Structured Term Entries: Defines a five-field entry shape (definition, owner, aliases, not-to-be-confused-with, dates) where each field prevents a specific class of ambiguity. - Add and Retire Discipline: Provides signals for when a term is load-bearing and contested enough to add, and requires explicit deprecation with pointers rather than silent deletion when terms retire. - Ambiguity Tracing: Treats recurring "what do you mean by X?" spec review comments as glossary bug reports, tracing ambiguous acceptance criteria back to missing or drifted entries. - Use Case: During a spec review, a reviewer flags "notify the user" as ambiguous because an Account has many users. Use this Skill to add a glossary entry distinguishing User from Account, then reference it by slug so the next spec does not reintroduce the ambiguity. ## Quick Start Ask the agent to create or update the domain glossary entry in .hero/knowledge for a contested term that came up in spec review.
