Individual skill

spk-doctrine-glossary

Curate and apply Spec Kitty glossary terminology, aliases, conflicts, semantic drift checks, and domain-model pressure-tests.

tests/fixtures/charter_pack_cutover/static/removed_skills/spk-doctrine-glossary/SKILL.md

Read pinned source

Source commit 25b7cd4fbc8f42ec71219408e2b5d76e7dae38b4

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,717
Repository last updated: Nov 7, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
gemini-cli Repository topic
spec-driven-development Repository topic
cursor-agent Repository topic
github-copilot Repository topic
windsurf Repository topic
ai-coding-workflow Repository topic
ai-development-dashboard Repository topic
ai-progress-tracking Repository topic
coding-agent-orchestration Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 880 bytes

Read excerpt


# spk-doctrine-glossary

Use this skill when the user asks about canonical terms, glossary updates,
terminology drift, or domain language consistency.

## Flow

1. Locate active glossary context.
2. Classify the change: new term, alias, conflict, drift, or usage correction.
3. When shaping a domain model or resolving a contested term, use the detailed
   `spec-kitty-glossary-context` workflow to pressure-test the model before
   recording it.
4. Update or apply terminology without rewriting unrelated docs.
5. Feed domain language back into spec, plan, and documentation skills.