Validates and registers new SoT IDs with cross-reference integrity.

MITAuto-check passedResearch & Science

Install Ghm Id Register

skills CLI
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill ghm-id-register -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mattgierhart/PRD-driven-context-engineering ghm-id-register --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ghm-id-register .claude/skills/ghm-id-register && rm -rf skills-src

Use ~/.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/

Facts

Skill name
ghm-id-register
GitHub stars
180
Token cost
~1.5k tokens
SKILL.md length
582 words
Files
4 (incl. references, assets)
Skills in repo
45
Repo updated
First seen
Licence
MIT

At a glance

Validates and registers new SoT IDs with cross-reference integrity.

  • Works in 5 steps: Validate Format → Check Uniqueness → Verify Cross-References → …
  • Creating BR-XXX
  • SKILL.md covers Workflow Overview, Core Output Template, ID Format Reference and Step 1: Validate Format, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ghm Id Register is an agent skill from mattgierhart/PRD-driven-context-engineering. Validates and registers new SoT IDs with cross-reference integrity. Triggers when creating BR-XXX, UJ-XXX, API-XXX, or CFD-XXX entries. Outputs formatted SoT entry with validated cross-references.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files and assets (for example `assets/id-validation-checklist.md`, `references/cross-reference-patterns.md` and `references/examples.md`).

It sits in Research & Science, covering Physical and earth sciences. The repository describes itself as: PRD-Led Context Engineering — Memory as Infrastructure. An ontology layer for product teams building products that solve real problems — with AI agents that remember. Gated PRD… The licence is MIT.

When your agent uses it

  • Creating BR-XXX
  • CFD-XXX entries

Example prompts

  • “Use the ghm-id-register skill to validate and registers new SoT IDs with cross-reference integrity”
  • “/ghm-id-register”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Grep

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Validate Format
  2. Check Uniqueness
  3. Verify Cross-References
  4. 5: Evaluate Confidence (NEW)
  5. Register Entry

What it can do on your machine

Read from SKILL.md and the folder at commit 30ed1b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Grep

    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

Ghm Id Register loads about 1.5k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 582 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.9k

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 mattgierhart/PRD-driven-context-engineering at commit 30ed1b0, republished under its MIT licence (© mattgierhart). 582 words, ~1,518 tokens.

Download SKILL.mdSave it as .claude/skills/ghm-id-register/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
ghm-id-register
description
Validates and registers new SoT IDs with cross-reference integrity. Triggers when creating BR-XXX, UJ-XXX, API-XXX, or CFD-XXX entries. Outputs formatted SoT entry with validated cross-references.
allowed-tools
Read, Write, Edit, Grep
context
fork

ID Register

Validate and register new Source of Truth IDs with cross-reference integrity checks.

Workflow Overview

  1. Validate Format → Check ID follows [PREFIX]-[3-digit] pattern
  2. Check Uniqueness → Ensure ID doesn't already exist
  3. Verify Cross-Refs → All referenced IDs must exist
  4. Register Entry → Add to appropriate SoT file

Core Output Template

ElementDefinitionEvidence
IDUnique identifierBR-101, UJ-045, API-012
TitleShort descriptive nameClear, specific
Cross-ReferencesLinks to related IDsAll referenced IDs exist
StatusCurrent stateDraft / Active / Deprecated

ID Format Reference

PrefixDomainFile
BR-Business RulesSoT/SoT.BUSINESS_RULES.md
UJ-User JourneysSoT/SoT.USER_JOURNEYS.md
API-API ContractsSoT/SoT.API_CONTRACTS.md
CFD-Customer FeedbackSoT/SoT.customer_feedback.md

Step 1: Validate Format

Check ID follows the pattern:

[PREFIX]-[XXX]

Where:

  • PREFIX = BR, UJ, API, or CFD
  • XXX = 3-digit number (zero-padded)
Checklist
  • Prefix is valid (BR, UJ, API, CFD)
  • Number is 3 digits
  • Format matches [A-Z]+-[0-9]{3}

Step 2: Check Uniqueness

  1. Read target SoT file
  2. Extract all existing IDs of same prefix
  3. Verify new ID doesn't exist
  4. If auto-assigning: use highest existing + 1
Checklist
  • Target SoT file read
  • Existing IDs enumerated
  • New ID is unique

Step 3: Verify Cross-References

For each ID referenced in the new entry:

  1. Identify the prefix
  2. Check that ID exists in its SoT file
  3. Flag any missing references
Checklist
  • All BR-XXX references exist in BUSINESS_RULES
  • All UJ-XXX references exist in USER_JOURNEYS
  • All API-XXX references exist in API_CONTRACTS
  • All CFD-XXX references exist in CUSTOMER_FEEDBACK
  • Each cross-reference includes a relationship type (see references/cross-reference-patterns.md)
  • Relationship types match the directional hierarchy (vertical types for cross-layer, lateral types for same-layer)

Step 3.5: Evaluate Confidence (NEW)

Before registering, assign a confidence score (1-5) based on evidence strength:

ScoreEvidence LevelExamples
1/5Assumption / PM decision"We think users want X"
2/5Secondary researchCompetitive analysis, market report
3/5Direct feedbackUser interviews (3-5 conversations)
4/5Validated behaviorBeta testing, small-scale usage
5/5Production evidenceReal usage data at scale

Question to ask: What's the highest evidence supporting this entry right now? What would move it to the next confidence level?

Example confidence annotations:

  • confidence: 2/5, source: competitive-analysis
  • confidence: 3/5, source: 5-user-interviews-jan-2026
  • confidence: 4/5, source: beta-cohort-validation

See .claude/skills/PRINCIPLES.md for detailed confidence model by SoT type.

Show full SKILL.md (222 more words)Show less
Checklist
  • Confidence score assigned (1-5)
  • Highest evidence source identified
  • Forward path identified ("would move to X/5 if...")

Step 4: Register Entry

Add formatted entry to SoT file:

markdown
### [ID]: [Title]

**Status**: Draft
**Created**: YYYY-MM-DD
**Confidence**: [1-5]/5 (source: [evidence source])
**Next Confidence Target**: [What would move this to next level]
**Cross-References**: [List of related IDs]

[Description]

**Acceptance Criteria**:
- [ ] Criterion 1
- [ ] Criterion 2

Example entry with confidence:

markdown
### CFD-042: Users want dark mode

**Status**: Active
**Created**: 2026-02-01
**Confidence**: 3/5 (source: 5-user-interviews-jan-2026)
**Next Confidence Target**: 4/5 (would require beta cohort validation)
**Cross-References**: FEA-008 (dark mode feature)

During interviews, 4 of 5 users mentioned desire for dark mode. Competitors (Notion, Linear, Figma) all have it.

**Acceptance Criteria**:
- [ ] Feature FEA-008 delivered to beta cohort
- [ ] Track usage: % of beta users enabling dark mode

Quality Gates

Pass Checklist
  • ID format is valid
  • ID is unique within its domain
  • All cross-references resolve
  • Entry follows SoT template
  • Confidence score assigned (1-5) with source documented
  • Next confidence target identified
Testability Check
  • ID can be searched and found
  • Cross-references are bidirectional (if required)
  • Confidence score is honest (reflects actual evidence, not wishful thinking)

Anti-Patterns

PatternExampleFix
Duplicate IDCreating BR-101 when it exists→ Check uniqueness first
Orphan referenceReferences UJ-999 that doesn't exist→ Verify all cross-refs
Wrong prefixUsing BR- for an API contract→ Match prefix to domain
Missing zero-padBR-5 instead of BR-005→ Always use 3 digits
Inflated confidenceAssigning 4/5 to a PM assumption→ Be honest about evidence level
No confidence source"confidence: 3/5" with no source→ Always record source (CFD-001, user-interview-jan, etc.)
Missing confidence targetConfidence assigned but no forward path→ Ask "what would move this to 4/5?"

Boundaries

DO:

  • Format validation
  • Uniqueness checks
  • Cross-reference verification
  • Entry formatting

DON'T:

  • Content decisions about ID meaning
  • Approve/reject based on business logic
  • Modify existing IDs

Handoff

After ID registration:

  • New ID is in SoT file
  • Cross-references are valid
  • EPIC Execution Plan updated with new ID
  • Ready for implementation

© mattgierhart, 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 3 other files (references, assets) in .claude/skills/ghm-id-register of mattgierhart/PRD-driven-context-engineering.

  • SKILL.md
  • assets/id-validation-checklist.md
  • references/cross-reference-patterns.md
  • references/examples.md

Open the folder on GitHubat commit 30ed1b0

Compare with similar skills

Ghm Id Register 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.

Ghm Id Register compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ghm Id Register this skillmattgierhart/PRD-driven-context-engineering180—~1.5kAutomated safety check: PassMIT
AstropyzLanqing/codex-claude-academic-skills4.7k13 repos~2.9kAutomated safety check: PassBSD-3-Clause
PymatgenzLanqing/codex-claude-academic-skills4.7k11 repos~5kAutomated safety check: PassMIT
Cantera Ignition DelayK-Dense-AI/scientific-agent-skills48k1 repos~2.2kAutomated safety check: PassMIT
Weathertrpc-group/trpc-agent-go1.9k8 repos~591Automated safety check: PassApache-2.0
Pymol VisualizationChatMol/ChatMol373—~1.2kAutomated safety check: PassMIT

Similar skills

  • Astropy

    zLanqing/codex-claude-academic-skills

    Comprehensive Python library for astronomy and astrophysics.

    4.7k GitHub starsUsed in 13 repos~2.9k tokens
    Research & ScienceAuto-check passed
  • Pymatgen

    zLanqing/codex-claude-academic-skills

    Materials science toolkit. An agent skill from zLanqing/codex-claude-academic-skills.

    4.7k GitHub starsUsed in 11 repos~5k tokens
    Research & ScienceAuto-check passed
  • Cantera Ignition Delay

    K-Dense-AI/scientific-agent-skills

    Runs Cantera constant-volume or constant-pressure ignition simulations and reports temperature-based ignition delay with mechanism provenance and checks.

    48k GitHub starsUsed in 1 repo~2.2k tokens
    Research & ScienceAuto-check passed
  • Weather

    trpc-group/trpc-agent-go

    Get current weather and forecasts via wttr.in or Open-Meteo.

    1.9k GitHub starsUsed in 8 repos~591 tokens
    Research & ScienceAuto-check passed
  • Pymol Visualization

    ChatMol/ChatMol

    Generate publication-quality molecular visualization images using PyMOL.

    373 GitHub stars~1.2k tokensUpdated 6 mo ago
    Research & ScienceAuto-check passed
  • Review

    Muuuun/luxas

    Write domain-authentic review articles that synthesize rather than stack.

    1.2k GitHub stars~2.1k tokensUpdated 1 mo ago
    Research & ScienceAuto-check passed

More from mattgierhart/PRD-driven-context-engineering

All 45 skills in this repo
  • Ghm Gate Check

    mattgierhart/PRD-driven-context-engineering

    Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py).

    180 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check: notes
  • Ghm Harvest

    mattgierhart/PRD-driven-context-engineering

    Extracts durable insights from temp/ files to SoT during EPIC Phase E.

    180 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Ghm Sot Builder

    mattgierhart/PRD-driven-context-engineering

    Creates new Source of Truth (SoT) files when existing templates don't fit your needs.

    180 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed
  • Prd V01 Problem Framing

    mattgierhart/PRD-driven-context-engineering

    Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark.

    180 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Prd V01 User Value Articulation

    mattgierhart/PRD-driven-context-engineering

    Transform validated pain points into articulated user value statements for PRD v0.1 Spark.

    180 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Prd V02 Competitive Landscape Mapping

    mattgierhart/PRD-driven-context-engineering

    Map the competitive landscape before positioning your product for PRD v0.2 Market Definition.

    180 GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Ghm Id Register

What does Ghm Id Register do?

Validates and registers new SoT IDs with cross-reference integrity. Ghm Id Register is an agent skill from mattgierhart/PRD-driven-context-engineering. Validates and registers new SoT IDs with cross-reference integrity.

When should I use Ghm Id Register?

Ghm Id Register fits situations like: creating BR-XXX; CFD-XXX entries.

How do I install Ghm Id Register in Claude Code?

Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill ghm-id-register -a claude-code`. Or copy the skill folder (.claude/skills/ghm-id-register in mattgierhart/PRD-driven-context-engineering) into .claude/skills/ghm-id-register in your project. Claude Code loads it when a task matches its description.

How do I install Ghm Id Register in Codex?

Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill ghm-id-register -a codex`. Or copy the skill folder (.claude/skills/ghm-id-register in mattgierhart/PRD-driven-context-engineering) into .agents/skills/ghm-id-register in your project. Codex loads it when a task matches its description.

Can I use Ghm Id Register 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 mattgierhart/PRD-driven-context-engineering --skill ghm-id-register -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ghm-id-register, .gemini/skills/ghm-id-register, .github/skills/ghm-id-register and .opencode/skills/ghm-id-register in your project.

What does Ghm Id Register need to run?

SKILL.md names no scripts, command-line tools or credentials: Ghm Id Register is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep.

Does Ghm Id Register 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 Ghm Id Register 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 Ghm Id Register use?

Ghm Id Register 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 Ghm Id Register use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.

What are the alternatives to Ghm Id Register?

Skills that share tags, products or a category with Ghm Id Register: Astropy (zLanqing/codex-claude-academic-skills, 4.7k stars), Pymatgen (zLanqing/codex-claude-academic-skills, 4.7k stars), Cantera Ignition Delay (K-Dense-AI/scientific-agent-skills, 48k stars) and Weather (trpc-group/trpc-agent-go, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ghm Id Register?

mattgierhart (a GitHub user) maintains it in mattgierhart/PRD-driven-context-engineering, which has 180 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on August 31, 2026.

Source: mattgierhart/PRD-driven-context-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.