metodologia-data-governance

Design and operationalize data governance across catalog, ownership, classification, retention, and privacy compliance.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-data-governance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: metodologia-data-governance
Source: https://github.com/JaviMontano/metodologia-propuesta-agent-public/tree/main/.claude/skills/data/data-governance
Command: npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-data-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Data governance frameworks provide a complete blueprint to inventory, own, classify, retain, and protect data assets across complex, multi-domain estates, enabling trust, regulatory compliance, and faster decision-making.

Core Features & Use Cases

  • Data Catalog & Discovery: architect and operate metadata catalogs with technical and business context, lineage, and a business glossary.
  • Ownership & Stewardship: codify domain ownership, assign stewards, and establish RACI and governance councils for accountability.
  • Classification & Sensitivity: implement tiered data classification aligned to privacy and security controls across domains.
  • Retention & Lifecycle: define retention schedules, archiving, purging, and legal holds in a policy-driven approach.
  • Privacy & Compliance: automate privacy workflows (DSAR), consent management, DPIA, and audit trails for regulatory readiness.
  • Computational Governance: apply policy-as-code, data contracts, and federated governance patterns to operate at scale.
  • Use Case: a regulated financial organization can deploy data contracts and policy-driven controls to ensure cross-border data transfers stay compliant.

Quick Start

Map assets, owners, retention policies, and contracts, then generate the S1–S6 artifacts to deploy governance.

Frequently Asked Questions about metodologia-data-governance

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

FAQPage Schema
How do I operationalize data governance across a multi-domain data estate?▼

Operationalizing data governance requires codifying domain ownership, classifying data sensitivity, and applying policy-as-code to enforce auditable controls. This framework provides the blueprint to inventory, own, classify, and protect multi-domain data assets.

What is computational governance and how does it apply to data mesh environments?▼

Computational governance applies policy-as-code and data contracts to automate domain-level accountability at scale. In data mesh environments, it enables federated governance patterns to ensure auditable policies and cross-domain compliance without centralized bottlenecks.

How do I automate privacy compliance workflows for DSAR and consent management?▼

Automating privacy compliance workflows involves implementing DSAR processing, consent management, DPIA, and audit trails. This framework targets regulated industries to ensure regulatory readiness through policy-driven data controls and automated audit trails.

Can I use data contracts to manage cross-border data transfers in regulated financial organizations?▼

Data contracts enable regulated financial organizations to enforce policy-driven controls for cross-border data transfers. By codifying domain ownership and classification tiers, data contracts ensure cross-border transfers maintain regulatory compliance.

How do I establish domain ownership and stewardship for data governance councils?▼

Establishing domain ownership requires assigning data stewards and defining RACI matrices to enforce accountability. This framework codifies domain ownership and establishes governance councils to drive domain-level accountability across the data estate.

What is the best way to define data retention schedules and legal holds?▼

Defining data retention schedules requires a policy-driven approach to archiving, purging, and legal holds. This framework provides lifecycle management artifacts to map retention policies alongside data classification and ownership structures.