PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
A skill your agent uses when authoring or reviewing specs, requirements, design docs, ADRs, tasks, glossary entries, domain terms, technical terms, or wording consistency across artifacts
Install Glossary
$ npx skills add intent-driven-dev/intent-driven-template --skill glossary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install intent-driven-dev/intent-driven-template glossary --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/glossary .claude/skills/glossary && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "glossary" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/glossary into .claude/skills/glossary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glossary", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/glossaryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add intent-driven-dev/intent-driven-template --skill glossary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install intent-driven-dev/intent-driven-template glossary --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/glossary .agents/skills/glossary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "glossary" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/glossary into .agents/skills/glossary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glossary", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add intent-driven-dev/intent-driven-template --skill glossary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install intent-driven-dev/intent-driven-template glossary --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/glossary .cursor/skills/glossary && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "glossary" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/glossary into .cursor/skills/glossary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glossary", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/intent-driven-dev/intent-driven-template.git --path .agents/skills/glossary--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add intent-driven-dev/intent-driven-template --skill glossary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install intent-driven-dev/intent-driven-template glossary --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/glossary .gemini/skills/glossary && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "glossary" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/glossary into .gemini/skills/glossary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glossary", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install intent-driven-dev/intent-driven-template glossaryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add intent-driven-dev/intent-driven-template --skill glossary -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/glossary .github/skills/glossary && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "glossary" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/glossary into .github/skills/glossary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glossary", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add intent-driven-dev/intent-driven-template --skill glossary -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install intent-driven-dev/intent-driven-template glossary --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intent-driven-dev/intent-driven-template.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/glossary .opencode/skills/glossary && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "glossary" agent skill from https://github.com/intent-driven-dev/intent-driven-template/tree/main/.agents/skills/glossary into .opencode/skills/glossary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glossary", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
glossary- GitHub stars
- 159
- Token cost
- ~767 tokens
- SKILL.md length
- 303 words
- Files
- 2
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when authoring or reviewing specs, requirements, design docs, ADRs, tasks, glossary entries, domain terms, technical terms, or wording consistency across artifacts
- Works in 8 steps: Identify the artifact being authored or… → Read glossary/business.md and/or… → Extract project-specific, technical,… → …
- Reviewing specs
- SKILL.md covers Workflow, Glossary Files, Close-Term Question and Marking Terms in Artifacts, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Glossary is an agent skill from intent-driven-dev/intent-driven-template. Use when authoring or reviewing specs, requirements, design docs, ADRs, tasks, glossary entries, domain terms, technical terms, or wording consistency across artifacts
Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Development, covering Architecture decision records. The repository describes itself as: OpenSpec and OpenCode template for intent-driven development with specs, ADRs, C4 diagrams, Gherkin, TDD, Multi-Model Adversarial Spec Authoring, Glossary for Domain Terms, and… The licence is MIT.
When your agent uses it
- Reviewing specs
- Glossary entries
- Technical terms
- Wording consistency across artifacts
Example prompts
- “/glossary”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Identify the artifact being authored or reviewed.
- Read glossary/business.md and/or glossary/technical.md when present.
- Extract project-specific, technical, overloaded, ambiguous, or repeated concepts.
- Compare extracted concepts with existing glossary terms.
- If existing terms look close, ask the user whether to reuse one or define a new term.
- Use the chosen term consistently in the artifact.
- Add new terms to the appropriate glossary file.
- For non-glossary artifacts, create or update the artifact's companion glossary reference document.
What it can do on your machine
Read from SKILL.md and the folder at commit 73f54d5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Glossary loads about 767 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 303 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from intent-driven-dev/intent-driven-template at commit 73f54d5, republished under its MIT licence (© intent-driven-dev). 303 words, ~767 tokens.
Download SKILL.mdSave it as
.claude/skills/glossary/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- glossary
- description
- Use when authoring or reviewing specs, requirements, design docs, ADRs, tasks, glossary entries, domain terms, technical terms, or wording consistency across artifacts
Glossary
Use existing repository terms before creating new ones.
Workflow
- Identify the artifact being authored or reviewed.
- Read
glossary/business.mdand/orglossary/technical.mdwhen present. - Extract project-specific, technical, overloaded, ambiguous, or repeated concepts.
- Compare extracted concepts with existing glossary terms.
- If existing terms look close, ask the user whether to reuse one or define a new term.
- Use the chosen term consistently in the artifact.
- Add new terms to the appropriate glossary file.
- For non-glossary artifacts, create or update the artifact's companion glossary reference document.
Do not add generic dictionary words or one-off implementation details.
Glossary Files
glossary/business.md: domain, product, workflow, and business terms.glossary/technical.md: architecture, implementation, platform, and protocol terms.
If a needed glossary file is missing, create it with this table:
| Term | Definition | Use When | Avoid |
| --- | --- | --- | --- |New entries use the same table format. Keep definitions to one concise sentence.
Close-Term Question
Ask before creating a new term when existing terms may fit:
These glossary terms look close to "<concept>":
- `<existing-term>`: <why it may fit>
- `<another-term>`: <why it may fit>
Do you want to use one of these existing terms, or define a new term?Do not proceed with a new term until the user answers, unless no plausible existing term exists.
Marking Terms in Artifacts
In non-glossary artifacts, such as proposals, designs, specs, ADRs, and tasks, bold glossary terms that appear in the artifact's companion glossary reference.
Apply bolding in prose only. Do not bold terms in code blocks, frontmatter, links, or places where markdown formatting would make the artifact harder to read.
Companion Reference
Every authored or edited non-glossary artifact gets a companion file in the same directory.
Do not create companion glossary reference files for glossary source files themselves, such as glossary/business.md or glossary/technical.md.
Name: remove .md, then append -glossary-reference.md.
Examples: proposal-glossary-reference.md, design-glossary-reference.md, spec-glossary-reference.md, adr-glossary-reference.md, tasks-glossary-reference.md.
Format:
# Glossary Reference
| Term | Source Glossary | Context |
| --- | --- | --- |
| <Term> | `glossary/business.md` | <Short context for how the artifact uses this glossary term.> |Source Glossary is the glossary file the term came from or was added to, such as glossary/business.md or glossary/technical.md.
If no glossary terms are used, write:
# Glossary Reference
No glossary terms referenced.Do not copy definitions into companion files.
© intent-driven-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/glossary of intent-driven-dev/intent-driven-template.
- SKILL.md
- README.md
Open the folder on GitHubat commit 73f54d5
Compare with similar skills
Glossary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Glossary this skillintent-driven-dev/intent-driven-template | 159 | — | ~767 | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 380 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Improve Codebase Architectureywwynm/EverythingDone | 144 | 15 repos | ~1.3k | Automated safety check: Pass | GPL-3.0 | |
| Domain Modelingbrim-borium/spotify_sdk | 166 | 5 repos | ~806 | Automated safety check: Pass | Apache-2.0 | |
| Design Doc MermaidSpillwaveSolutions/design-doc-mermaid | 175 | 1 repos | ~5.6k | Automated safety check: Pass | None |
Similar skills
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
Learning Opportunities
DrCatHicks/learning-opportunities
Facilitates deliberate skill development during AI-assisted coding.
More from intent-driven-dev/intent-driven-template
All 10 skills in this repoAcceptance Test Authoring
intent-driven-dev/intent-driven-template
A skill your agent uses when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an…
Adversarial Authoring
intent-driven-dev/intent-driven-template
A skill your agent uses when rules or instructions mention "adversarial-authoring", "adversarial authoring", "must use adversarial-authoring skill", "model council", "cross-model review", or…
Architectural Decision Records
intent-driven-dev/intent-driven-template
A skill your agent uses when documenting, drafting, reviewing, or updating architectural decisions, ADRs, decision logs, tradeoffs, rationale, consequences, alternatives, or architecture decision…
Gherkin Authoring
intent-driven-dev/intent-driven-template
A skill your agent uses when drafting, reviewing, or improving Gherkin, Cucumber scenarios, BDD acceptance criteria, feature examples, Scenario Outlines, Backgrounds, Rules, Doc Strings, Data…
Openspec Bulk Apply Change
intent-driven-dev/intent-driven-template
A skill your agent uses when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
Spec As Source
intent-driven-dev/intent-driven-template
A skill your agent uses when a user or project explicitly adopts OpenSpec spec-as-source, fenced Gherkin specifications as executable acceptance tests, or acceptance-test-first OpenSpec tasks.
Related
Categories
Questions about Glossary
What does Glossary do?
A skill your agent uses when authoring or reviewing specs, requirements, design docs, ADRs, tasks, glossary entries, domain terms, technical terms, or wording consistency across artifacts. Glossary is an agent skill from intent-driven-dev/intent-driven-template.
When should I use Glossary?
Glossary fits situations like: reviewing specs; glossary entries; technical terms; wording consistency across artifacts.
How do I install Glossary in Claude Code?
Run `npx skills add intent-driven-dev/intent-driven-template --skill glossary -a claude-code`. Or copy the skill folder (.agents/skills/glossary in intent-driven-dev/intent-driven-template) into .claude/skills/glossary in your project. Claude Code loads it when a task matches its description.
How do I install Glossary in Codex?
Run `npx skills add intent-driven-dev/intent-driven-template --skill glossary -a codex`. Or copy the skill folder (.agents/skills/glossary in intent-driven-dev/intent-driven-template) into .agents/skills/glossary in your project. Codex loads it when a task matches its description.
Can I use Glossary in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add intent-driven-dev/intent-driven-template --skill glossary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/glossary, .gemini/skills/glossary, .github/skills/glossary and .opencode/skills/glossary in your project.
What does Glossary need to run?
SKILL.md names no scripts, command-line tools or credentials: Glossary is instructions for the agent only.
Does Glossary access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Glossary safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Glossary use?
Glossary is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Glossary use?
About 767 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Glossary?
Skills that share tags, products or a category with Glossary: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 380 stars), Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars) and Domain Modeling (brim-borium/spotify_sdk, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Glossary?
intent-driven-dev (a GitHub organization) maintains it in intent-driven-dev/intent-driven-template, which has 159 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 4, 2026.
Source: intent-driven-dev/intent-driven-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.