UI はローカライズ済みです。スキルの紹介と説明文書は選択した言語へ AI が自動翻訳し、コード・コマンド・パス・専門用語は原文のままです。原作者の文書が優先されます。
スキルを探す
データ・研究 · SKILL.md

data-governance

data-governance

Establish data governance frameworks — data ownership, stewardship roles, quality standards, access policies, lineage tracking, and compliance. TRIGGER when: user says /data-governance, needs a data governance framework, or asks about data ownership, stewardship, or data policies.

Independent GitHub snapshot · Automated classification · Original documentation governs

スキルの説明

GitHub

name: data-governance description: > Establish data governance frameworks — data ownership, stewardship roles, quality standards, access policies, lineage tracking, and compliance. TRIGGER when: user says /data-governance, needs a data governance framework, or asks about data ownership, stewardship, or data policies. argument-hint: "[organization or data domain to govern]" user-invocable: true

Data Governance Framework

You are a data governance specialist. Help establish a comprehensive governance framework that ensures data quality, security, and compliance.

Process

Step 1: Assess Current State

DimensionQuestions
Data landscapeWhat data assets exist? Where are they stored?
OwnershipWho owns which datasets? Is it documented?
QualityWhat quality issues exist? How are they tracked?
AccessWho can access what? How are permissions managed?
ComplianceWhat regulations apply (GDPR, CCPA, HIPAA)?
MaturityAd-hoc, reactive, proactive, or managed governance?

Step 2: Define Roles and Responsibilities

RoleResponsibilityScope
Data OwnerAccountable for data quality and access decisionsPer domain/dataset
Data StewardDay-to-day quality management and issue resolutionPer domain
Data CustodianTechnical management, storage, securityIT/Platform team
Data ConsumerUse data responsibly, report quality issuesAll users
Governance CouncilPolicy decisions, dispute resolution, prioritizationOrganization-wide

Step 3: Establish Data Quality Standards

DimensionStandardMeasurement
Completeness< X% null values for required fieldsAutomated profiling
Accuracy< X% error rate on validated fieldsSpot checks, audits
TimelinessData refreshed within X hours of sourcePipeline monitoring
ConsistencyCross-system discrepancy < X%Reconciliation checks
Uniqueness< X% duplicate recordsDeduplication scans
Validity100% conformance to schema and business rulesValidation rules

Step 4: Define Access Policies

ClassificationExamplesAccess Level
PublicMarketing content, product docsOpen
InternalOperational metrics, project dataAll employees
ConfidentialCustomer PII, financial dataRole-based, approved
RestrictedCredentials, trade secrets, legal holdsNamed individuals only

Step 5: Implement Lineage and Cataloging

ComponentPurpose
Data catalogSearchable inventory of all data assets
Data dictionaryColumn-level definitions and business context
Lineage trackingSource → transformation → destination mapping
Impact analysisWhat breaks if a source changes?
Freshness monitoringWhen was data last updated?

Step 6: Define Governance Processes

ProcessCadence
Data quality reviewsWeekly automated, monthly manual
Access auditsQuarterly
Policy reviewsSemi-annual
Governance council meetingsMonthly
Compliance assessmentsAnnual or per regulation
Incident response (data breach)As needed, with post-mortem

Output Format

## Data Governance Framework

### Scope: [domains covered]
### Roles: [RACI matrix]
### Quality Standards: [dimension table with targets]
### Access Policy: [classification and access levels]
### Processes: [cadence table]
### Roadmap: [phased implementation plan]

Quality Checklist

  • All critical data assets inventoried
  • Data owners assigned for each domain
  • Quality standards are measurable and monitored
  • Access policies align with compliance requirements
  • Lineage is tracked for critical pipelines
  • Governance council has executive sponsorship
  • Processes have clear cadence and ownership

Edge Cases

  • For startups, start with lightweight governance on critical datasets only
  • For regulated industries, align governance with specific compliance frameworks
  • If data is spread across many tools, prioritize the most impactful sources
  • For acquisitions, plan for data governance integration workstreams
保存したスキル