adversarial-squad
Deploy a bounded, profile-loaded adversarial review squad at a mission point-cut so…
Curate and apply Spec Kitty glossary terminology, aliases, conflicts, semantic drift checks, and domain-model pressure-tests across missions. Triggers: "update the glossary", "use canonical terms", "check terminology", "add a term", "fix term drift", "glossary conflicts",
$ npx -y skills add spec-kitty/spec-kitty --skill spk-charter-glossary --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/spk-charter-glossaryContext preview
The summary Claude sees to decide when to auto-load this skill.
Curate and apply Spec Kitty glossary terminology, aliases, conflicts, semantic drift checks, and domain-model pressure-tests across missions. Triggers: "update the glossary", "use canonical terms", "check terminology", "add a term", "fix term drift", "glossary conflicts",
name: spk-charter-glossary description: >- Curate and apply Spec Kitty glossary terminology, aliases, conflicts, semantic drift checks, and domain-model pressure-tests across missions. Triggers: "update the glossary", "use canonical terms", "check terminology", "add a term", "fix term drift", "glossary conflicts", "resolve ambiguity", "review terminology consistency", "shape a domain model's terms", "validate domain language against code". Does NOT handle: runtime loop advancement, setup or repair requests, agent configuration, or direct code implementation tasks.
Maintain semantic integrity by curating the project glossary, detecting term drift, and ensuring that all mission artifacts use canonical terminology.
Use this skill when the user asks about canonical terms, glossary updates, terminology drift, or domain language consistency. Do not use it for purely operational tasks like advancing the runtime loop or repairing an installation.
1. Locate active glossary context. 2. Check conflicts and strictness before changing anything. 3. Classify the change: new term, alias, conflict, drift, or usage correction. 4. When shaping a domain model or resolving a contested term, pressure-test the model before recording it: cross-check code evidence, challenge the term with a concrete edge case, and apply the ADR gate. 5. Update or apply terminology without rewriting unrelated docs. 6. Feed domain language back into spec, plan, and documentation skills.
middleware pipeline, events), and the detailed steps for locating context, resolving conflicts, pressure-testing terms, and preventing drift.
status lifecycle, event-sourcing mechanics, and CLI quick reference.
detection and correction strategies.
Spec-Driven Development with organizational governance. Specs tell AI agents what to build; Charter governs how they build it. Git-native missions, enforceable workflows, and consistent engineering standards across AI coding agents and harnesses.
Deploy a bounded, profile-loaded adversarial review squad at a mission point-cut so…
Understand how Spec Kitty manages git: what git operations Python handles automatically, what…
Orchestrate the implement-review loop for Spec Kitty work packages using any configured…
Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify…
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define…
Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows…