spk-doctrine-glossary

Locate the active glossary context, classify each change as a new term, alias, conflict, drift, or usage correction, then apply the update. Canonical terms are fed back into spec, plan, and documentation artifacts to keep language consistent.

Terminology drift is detected by comparing current usage against the canonical glossary and classifying deviations as drift or conflicts. The Skill then applies corrections to the affected terms without rewriting unrelated documents.

An alias is an accepted alternative name mapped to a canonical term, while a conflict occurs when two terms compete for the same concept without resolution. The Skill classifies each case so aliases are recorded and conflicts are resolved to a single canonical term.

Yes, the Skill defines spec-kitty-glossary-context as a legacy alias for detailed glossary workflows and field guides. When that skill is available, it can be used for more in-depth glossary operations.

Avoid it for one-off documents or projects without shared domain language, where maintaining a canonical glossary adds overhead without benefit. It is designed for repositories where specs, plans, and docs must stay terminologically consistent.