mcpField
R
revops-crm-governance-review

revops-crm-governance-review

github.com/sylphxaiMarketing & growth136 installsUpdated today
Repository

About revops-crm-governance-review

A RevOps CRM governance skill for teams defining lifecycle, routing, forecasting, attribution, ownership, and data-quality practices. It turns governance questions into operational artifacts with owners, controls, metrics, and recovery plans.

Key features

  1. 01Classify CRM governance work
  2. 02Define object ownership and field rules
  3. 03Specify lifecycle and automation controls
  4. 04Create data-quality checks
  5. 05Plan rollout and backfill

Use cases

  1. 01Design lifecycle stages and exit criteria
  2. 02Review lead routing and ownership
  3. 03Govern attribution and pipeline reporting
  4. 04Plan CRM integration or permission changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill revops-crm-governance-review

After installing, type/revops-crm-governance-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/revops-crm-governance-patterns.md

Details

From the project README

RevOps CRM Governance Review

Use this skill to convert RevOps CRM governance, lifecycle stage, routing, forecast, attribution, owner, and data-quality questions into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify CRM objects, revenue motion, lifecycle stages, owner teams, integrations, reporting dependencies, forecast process, current data-quality issues, and governance owner.
  2. Read references/revops-crm-governance-patterns.md.
  3. Classify work as lifecycle design, routing, required-field policy, pipeline stage hygiene, attribution, duplicate cleanup, integration change, permission review, or reporting governance.
  4. Define object ownership, field definitions, stage exit criteria, automation rules, change approval, data-quality checks, and reporting contracts.
  5. Produce CRM governance plan, state machine, decision table, event schema, data-quality checklist, and rollout/backfill plan.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not let reports, automations, routing, and compensation depend on undefined or manually inconsistent fields.
  • Do not change CRM stages, attribution, or ownership without migration, training, and downstream-report impact review.
  • Do not make reps do low-value admin work when automation or simpler stage design can preserve data quality.
  • Do not treat CRM as finance truth, product usage truth, or support truth without reconciliation boundaries.

Output format

CRM governance context:
Audience / source of truth / risk boundary:

Revenue operations plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Lifecycle, fields, automation, and data-quality controls:
- <trigger> -> <policy, metric, edge case, support note>

Comments

Markdown supported