- name
- ssotize
- description
- Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or platforms. Starts read-only, reports the map and plan, then mutates only after explicit approval.
Find every copy of one scattered fact, consolidate it into one canonical home after approval, and replace the rest with references.
Goal
One fact has one home, and every other place references it: references do not drift, copies do. ssotize establishes or repairs that state in messy, legacy, or freshly scaffolded work. Consolidation is deliberate and loses no information, and it is a one-time repair: once SSOT holds, the fact needs no further consolidation.
The skill starts as a read-only audit that names the truth, finds every copy, chooses the canonical home, and reports the exact plan. It mutates only after the user approves that plan. The audit and the consolidation stay in one workflow with the approval gate between them, because a separate checker makes the audit easy to skip.
Workflow
- Name the truth in scope: the specific fact, value, spec, decision, status, or definition being tracked, not the whole document.
- Audit read-only. List every occurrence across the given artifacts and platforms. For the candidate occurrences that are files, run
node scripts/snapshot-candidates.mjs [--json] <path>...from this skill's folder: it prints path, mtime, size and sha256 per file (directories walked) as a Markdown table, or JSON with--json, and exits 2 on a usage error or an unreadable path. Report that table. - Enumerate again by a second method (another search term, a synonym, or another tool) and confirm it finds nothing the first pass missed.
- Classify each occurrence by kind: exact copy, paraphrase, partial, stale, contradictory.
- Choose the canonical home: the most authoritative and most maintained location, closest to where the fact changes. Never promote a weak copy for convenience; when no location qualifies, extract a new canonical home. A figure another system already answers (a count, a release, a price, a date) has that system as its home: every occurrence becomes a read from it when the artifact is built or served, and where the system cannot answer, the sentence is hidden rather than filled from memory, since a typed copy starts going stale the day it ships.
- Choose an action for each non-canonical occurrence:
- dedupe: a redundant copy.
- reference: docs link to the canonical home, code imports, sources, or includes it, and config reads a shared file.
- reconcile: the occurrence disagrees and needs a human call.