spec-kitty-glossary-context

Prevent terminology drift by extracting terms from step inputs and outputs, then validating them against a canonical glossary using scope precedence to resolve conflicts. This enforces a consistent semantic contract across all project artifacts.

Scope precedence in glossary conflict resolution determines which definition wins when terms overlap. Mission_local scope overrides team_domain, ensuring context-specific definitions take priority over broader project terminology.

Detect semantic validation conflicts by running a glossary inspection command that extracts terminology from step inputs and outputs and checks them against canonical definitions. Identified conflicts are then resolved through interactive or non-interactive flows.

Yes, you can block generation using configurable strictness gating set to off, medium, or max. Max strictness blocks generation when unresolved semantic conflicts are detected, preventing ambiguous terminology from degrading consistency.

Event sourcing reconstructs glossary state by replaying terminology update events chronologically, allowing recovery of canonical definitions at any checkpoint. This supports glossary upkeep and conflict inspection without losing historical term definitions.

Use strictness gating for terminology validation when missions risk semantic drift or ambiguity. Max strictness blocks generation on unresolved conflicts, medium allows warnings, and off skips checks entirely for low-stakes contexts.