$ loading_
提取并维护领域术语表，统一规范术语、识别歧义并校验文档一致性。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "domain-glossary" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/domain-glossary/SKILL.md 2. 保存为 ~/.claude/skills/domain-glossary/SKILL.md 3. 装好后重载技能，告诉我可以用了
请基于这份 PRD、技术方案和用户故事，提取领域术语表。为每个术语给出规范名称、定义、常见同义词、易混淆项、是否存在歧义，以及与其他术语的关系映射。最后标出需要团队确认的冲突术语。
一份结构化领域术语表，包含规范术语、同义词、歧义标记、术语关系和待确认问题清单。
请检查以下规格说明、ADR 和任务单中的术语是否一致。找出同一概念被不同名称描述的情况、同一术语指代多个概念的情况，并给出统一建议术语及替换清单。
一份术语一致性审查结果，列出冲突点、风险说明、统一建议和逐项替换方案。
我正在编写一份新规范，请根据现有项目文档先建立基础领域术语表，并检查我草稿中的术语是否符合既有定义。若发现新术语，请判断是否应纳入术语表，并说明与现有术语的关系。
一份可用于规范编写的基础术语表，以及针对草稿术语的合规性检查与新增建议。
Enterprise systems accumulate terminology debt: the same concept called different names across teams, specs, and code. Synonym drift corrupts search, work-item labeling, and cross-spec consistency. A shared canonical glossary reduces misunderstanding and improves spec-to-code traceability.
This skill has two modes: extract (build or update a glossary) and validate (check an artifact against the glossary).
| Trigger | Action |
|---|---|
New feature spec created (devsquad.specify) | Extract terms from the spec |
Envisioning completed (devsquad.envision) | Extract terms from the envisioning document |
| Domain discussion in conversation | Extract terms as they emerge |
| Explicit user request ("build a glossary", "define domain terms") | Full extraction from available artifacts |
| Review finding: inconsistent terminology |
| Update glossary with canonical choice |
docs/domain/GLOSSARY.md (or create from template if it does not exist)docs/features/**/spec.md)docs/envisioning/*.md)docs/architecture/decisions/*.md)docs/domain/GLOSSARY.md using the format below# Domain Glossary
## [Domain Group]
| Term | Definition | Status | Aliases to avoid |
|------|-----------|--------|-----------------|
| **[Term]** | [One sentence: what it IS, not what it does] | [Established/Proposed/Contested] | [Synonyms to avoid] |
## Relationships
- A **[Term A]** belongs to exactly one **[Term B]**
- A **[Term C]** produces one or more **[Term D]**
## Flagged Ambiguities
- "[word]" was used to mean both **[Term X]** and **[Term Y]**. These are distinct concepts: [explanation of the difference and recommended usage].
GLOSSARY.md when the first terms are resolved; do not bloat new projects| Level | Criterion |
|---|---|
| Established | Term appears consistently in accepted specs and ADRs |
| Proposed | Term chosen during extraction but not yet validated by the team |
| Contested | Multiple stakeholders use different terms for the same concept |
Mark contested terms in the Flagged Ambiguities section until resolved.
| Agent | Artifact | Check |
|---|---|---|
devsquad.specify | spec.md | Terms used in the spec exist in the glossary; no synonym drift |
devsquad.review.spec | spec.md | Flag terms that contradict or diverge from the glossary |
…
帮助你创建、切换并检查代码分支，确保实现前遵循正确分支策略。
用于规划阶段创建与维护架构决策记录，自动检查重复性、完整性与相关参考信息。