spec-kitty-glossary-context

Name: spec-kitty-glossary-context
Availability: InStock
Author: kimprobably

Extract terms from step inputs and outputs and validate them against a scope-precedence glossary store.

Updated May 13, 2026

Search Tags:#glossary #conflict resolution #event sourcing #semantic validation #terminology drift #strictness gating #scope precedence

Ready to run

npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-glossary-context

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-kitty-glossary-context
Source: https://github.com/kimprobably/maestro-os/tree/main/.claude/skills/spec-kitty-glossary-context
Command: npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-glossary-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents terminology drift and ambiguity by validating mission artifacts against the project glossary, so missions keep a consistent semantic contract.

Core Features & Use Cases

Detects and resolves term drift by extracting terminology from step inputs/outputs, checking it against canonical glossary definitions, and identifying conflicts that would otherwise silently degrade consistency.
Blocks generation when required using configurable strictness (off/medium/max) and scope precedence (mission_local overrides team_domain, etc.) to avoid unresolved semantic conflicts.
Supports glossary upkeep and recovery through event-sourced state reconstruction, conflict inspection, and interactive/non-interactive conflict resolution flows.

Quick Start

Use the spec-kitty glossary conflicts command to identify any unresolved terminology issues before re-running or continuing a mission.

Frequently Asked Questions about spec-kitty-glossary-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent terminology drift across project artifacts?▼

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.

What is scope precedence in glossary conflict resolution?▼

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.

How do I detect semantic validation conflicts in mission artifacts?▼

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.

Can I block generation when unresolved terminology conflicts exist?▼

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.

How does event sourcing reconstruct glossary state?▼

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.

When should I use strictness gating for terminology validation?▼

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.