ghm-id-register_skill

Overview

This skill validates and registers new Source-of-Truth (SoT) IDs with cross-reference integrity checks. It enforces ID format, ensures uniqueness, verifies that all referenced IDs exist, and outputs a formatted SoT entry ready to append to the correct domain file. It triggers automatically for BR-XXX, UJ-XXX, API-XXX, and CFD-XXX entries.

How this skill works

When a new ID is created, the skill checks the prefix and zero-padded 3-digit pattern, then scans the target SoT file to confirm the ID is unique. It parses any referenced IDs, looks them up in their respective SoT files, and flags missing or mismatched references. If all gates pass, it produces a standardized markdown entry with status, creation date, cross-references, description placeholder, and acceptance criteria for registration.

When to use it

• When creating a new business rule (BR-XXX) entry
• When adding a new user journey (UJ-XXX) item
• When registering a new API contract (API-XXX)
• When logging customer feedback items (CFD-XXX)
• When you need to ensure cross-reference integrity across SoT files

Best practices

• Always use the correct prefix for the domain (BR, UJ, API, CFD)
• Keep IDs zero-padded to three digits (e.g., BR-005) to avoid formatting errors
• Run the uniqueness check before editing content to prevent duplicate IDs
• Include all related IDs in Cross-References and resolve them prior to registration
• Use the generated template fields (Status, Created, Cross-References, Acceptance Criteria) to maintain consistency

Example use cases

• Auto-assign the next available BR-XXX when creating new business rules
• Validate that a new API contract references only existing UJ-XXX and BR-XXX entries
• Prevent registration of CFD-XXX that cites nonexistent product or journey IDs
• Produce a ready-to-paste SoT entry for PRD or implementation handoff
• Gate deployment readiness by ensuring cross-references are bidirectional if required