cdo-review

Interrogates data strategy plans using six Chief Data Officer decision questions.

25.3k|3.6k|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/alirezarezvani/claude-skills --skill cdo-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdo-review
Source: https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/cdo-review
Command: npx skills add https://github.com/alirezarezvani/claude-skills --skill cdo-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans involving training data, data architecture, data productization, or data team hiring often proceed without rigorous scrutiny of consent provenance, architecture fit, asset value, or hiring sequencing, leading to compliance exposure and costly wrong decisions.

Core Features & Use Cases

  • Six CDO Forcing Questions: Pressure-tests any plan across decision rationale, consent provenance, consumer count, M&A readiness, source dependency, and hiring fit.
  • Decision-Driven Workflow: Routes to companion scripts for AI training data audits, warehouse/lakehouse/mesh architecture selection, and data asset valuation.
  • Structured Verdict Output: Produces a SHIP, SHARPEN, or BLOCK verdict with remediation steps and routing to GC, CISO, CFO, and CHRO reviews.
  • Use Case: Before training a model on customer data, run the review to audit consent provenance per source, classify sources as GO, MITIGATE, or NO-GO, and document the verdict for M&A diligence.

Quick Start

Ask the AI to run a CDO review on your data productization plan to validate consent provenance, architecture choice, and asset value before committing.

Frequently Asked Questions about cdo-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate training data consent before an ML project?

Run the AI training data audit script with a JSON file of your data sources to classify each as GO, MITIGATE, or NO-GO based on consent provenance. The review checks origin, consent flow, data class, and intended use for every source.

How do I choose between warehouse, lakehouse, and data mesh?

The choice depends on internal consumer count: under 5 consumers favors a warehouse, 5-25 favors a lakehouse, and 25+ with federated culture favors mesh. The data product strategy picker script formalizes this decision from a profile JSON input.

When should I run a CDO review on a plan?

Run it before approving ML training on customer data, signing multi-year data infrastructure contracts, productizing customer data, making major data hires, or entering M&A diligence. It also applies whenever data monetization is proposed.

Can this review help with M&A data diligence?

Yes, it checks anonymization documentation, MSA carve-out coverage, and training-data provenance logs. The data asset valuator script estimates strategic value, moat strength, and ARR multiplier ranges for the data corpus.

What are the limitations of this review framework?

It is a decision framework, not a legal opinion, so productization or licensing paths still require routing to general counsel review. It also depends on accurate JSON inputs describing data sources and organizational profile.