ghm-sot-builder_skill

Overview

This skill creates new Source of Truth (SoT) files when existing templates don't cover a required artifact type. It outputs a properly structured SoT.*.md file with YAML frontmatter, ID prefix rules, category ranges, entry templates, and an update protocol. Use it sparingly for durable, cross-referenced artifacts that need unique IDs.

How this skill works

It inspects whether an existing SoT can host the artifact and guides schema design when a new file is necessary. The skill generates a pure template: frontmatter (version, purpose, id_prefix, authority), navigation, repeatable entry template, cross-reference index, and an explicit update protocol. It also returns registration steps to add the prefix to the unique-ID registry and to update the SoT index.

When to use it

• You need to track a durable artifact not covered by current SoT files
• You require a unique ID prefix and cross-references for a new artifact type
• You must consolidate scattered documentation into a canonical SoT file
• You fork the repo and existing SoT templates don’t fit your domain
• You want a template that enforces structure and update protocol

Best practices

• Confirm no existing SoT fits before creating a new file
• Choose a 2–4 uppercase letter ID prefix and check uniqueness in the ID registry
• Design required fields and category ranges before drafting the file
• Keep methodology and best-practice content out of the template (move to skill references)
• Include an explicit Update Protocol and cross-reference integrity checks

Example use cases

• Create SoT for Partner Integration Contracts with prefix PIC and category ranges for active/archived agreements
• Add a SoT for Migration Plans when the current files lack migration-specific fields
• Consolidate scattered API extension notes into a single SoT with bidirectional cross-references
• Register a new internal artifact type used by multiple teams so entries are discoverable by ID search
• Generate a pure template for domain-specific fields (e.g., partner contact, contract URL) without prescribing evaluation criteria