write-terms

Generate a consistent term registry with frontmatter and change tracking.

1|Updated Jan 15, 2026

Search Tags:#documentation #consistency #frontmatter #terms #terminology #workaholic

Ready to run

npx skills add https://github.com/qmu/workaholic --skill write-terms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-terms
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/write-terms
Command: npx skills add https://github.com/qmu/workaholic --skill write-terms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides structured governance for terminology by defining and updating terms in .workaholic/terms/ to ensure consistent language across tickets, specs, and developer guides.

Core Features & Use Cases

Term standardization: Creates a central, searchable registry of terms used throughout the project.
Change tracking & governance: Updates are tracked with commit hashes and last_updated metadata, enabling audits and onboarding.
Operational workflow integration: Supports automated updates via the bundled gather.sh script to surface changes and affected terms.

Quick Start

Run the bundled gather script to surface changes and available terms:

bash .claude/skills/write-terms/sh/gather.sh [base-branch]

Frequently Asked Questions about write-terms

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

FAQPage Schema

How do I maintain consistent terminology across software documentation and tickets?▼

To maintain consistent terminology, you can use a frontmatter-driven term registry within the .workaholic/terms/ directory. This centralizes project language, ensuring consistent usage across specifications and developer guides.

What is a term registry and how does it track documentation changes?▼

A term registry is a central directory of standardized project language that tracks documentation changes using last_updated timestamps and commit_hash metadata. This enables governance by linking terminology updates directly to repository history.

How do I automate gathering terminology updates from a base branch?▼

You automate gathering terminology updates by running the bundled gather.sh script via bash .claude/skills/write-terms/sh/gather.sh [base-branch]. This surfaces available terms and recent changes without manual file searching.

Can I integrate term governance into my existing software maintenance workflow?▼

Yes, term governance integrates into existing software maintenance workflows by applying a structured frontmatter format to term files. This enforces consistent language across proposals and documentation updates.

What's the best way to standardize project language for developer onboarding?▼

The best way to standardize project language for developer onboarding is implementing a searchable term registry with commit hash tracking. This provides clear historical context and enforces consistent language across project documentation.

Does term governance require manual updates for every new project term?▼

No, term governance does not require manual updates for every new term. The bundled gather.sh workflow automates the process of surfacing changes and available terms from a specified base branch.