Crm Data Governance

by mbfinotti2dedb3934ca7MITListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 weeks ago

Design and operate CRM field-level governance - who owns each CRM field, which system is authoritative for it, how often it must be refreshed, and how the rules are enforced. Produces a field dictionary, per-field ownership, a system-of-record map with write-precedence and conflict rules, freshness SLAs, an enforcement plan, a field lifecycle, and a governance cadence. Use whenever the user mentions field ownership, single source of truth, system of record per field, data dictionary, stale CRM data, custom field sprawl, "which system wins", or "our CRM fields contradict each other" - even if they never say "governance". Covers B2B and B2C. Do NOT use for org-wide, object-level source-of-truth policy - use mbfinotti/revops-skills@revenue-data-governance-strategy instead.

Instructions onlyBusiness & Finance

Only the file list is public. File contents are available once the skill is installed in a workspace.

PathSizeType
evals/evals.json34.4 KBapplication/json
references/enforcement-menu.md6.8 KBtext/markdown
references/field-lifecycle.md4.3 KBtext/markdown
references/field-ownership-and-dictionary.md4.8 KBtext/markdown
references/freshness-slas.md2.8 KBtext/markdown
references/system-of-record-rules.md9.7 KBtext/markdown
references/worked-examples.md5.3 KBtext/markdown
SKILL.md19.1 KBtext/markdown

Source and attribution

Source:mbfinotti/revops-skillsinskills/crm-data-governanceat commit2dedb39

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal