metodologia-data-mesh-strategy

Assess data mesh readiness and design a phased adoption roadmap.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Data mesh adoption is complex and organizationally heavy; this skill provides a structured readiness assessment and a complete strategy to implement data mesh, including domain decomposition, data product design, platform requirements, governance, adoption roadmap, and organizational change.

Core Features & Use Cases

  • Readiness assessment based on Dehghani's four principles: Domain Ownership, Data as a Product, Self-Serve Platform, Federated Governance.
  • Domain decomposition and data product design with SLAs, data quality, and ownership mapping.
  • Platform requirements including build-vs-buy analysis and governance automation.
  • Adoption roadmap with phased milestones and org-change plans.
  • Guidance for pilot design, selective mesh, and hybrid patterns.

Quick Start

Provide a readiness assessment for your organization to determine if data mesh can be pursued, then draft a pilot for 1-2 domains and a phased expansion plan.

Frequently Asked Questions about metodologia-data-mesh-strategy

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

FAQPage Schema
How do I assess data mesh readiness for an organization with multiple domains?

Data mesh readiness assessment evaluates your organization against Dehghani's four principles: domain ownership, data as a product, self-serve platform, and federated governance. It analyzes platform constraints and governance needs to determine if a phased adoption strategy can be pursued.

How do I design a data product with SLAs and domain ownership mapping?

Data product design involves domain decomposition to define ownership, establish SLAs, and set data quality standards. This skill generates data product specifications that map specific domains to their respective owners and quality metrics.

What is the best way to plan a phased data mesh adoption roadmap?

A phased data mesh adoption roadmap starts with a readiness assessment, then drafts a pilot for 1-2 domains before expanding. It produces a 3- to 24-month plan with milestones, organizational change guidance, and hybrid pattern options.

Does my data platform need federated governance automation for a data mesh?

Federated governance automation is a core platform requirement for data mesh. This skill addresses governance, platform requirements, and build-vs-buy analysis to ensure your platform supports domain ownership and self-serve capabilities.

When should I not use a full data mesh architecture?

A full data mesh is not recommended if your organization lacks multiple domains or clear governance needs. This skill provides selective mesh and hybrid patterns, allowing a phased pilot approach rather than a full organizational overhaul.

Can I pilot a data mesh strategy without a complete organizational change?

Yes, you can pilot data mesh by drafting a strategy for 1-2 domains before a full rollout. This skill provides a phased adoption roadmap with organizational change plans tailored to specific pilot designs and selective mesh patterns.